Subversion FAQ
Fisheye Subversion FAQ
- Configuring Start Revision based on date — For Subversion repositories Fisheye has the ability to configure a Start Revision parameter to allow you to only index content from a given point in your repository.
- Errors 'SEVERE assert' or 'Checksum mismatch' — SVNKit may have problems with older version Subversion servers - versions 1.1.x and prior.
- Fisheye fails to connect to the Subversion repository after a short time of successful operation. — On Unix systems, the svn:// protocol is usually handled by inetd or xinetd. These daemons apply, by default, a connection per second limit to incoming connections. Any connections above this rate are rejected by the server.
- How can Fisheye help with merging of branches in Subversion? — In merge management, the main advantages of Fisheye come from its search functionality. If you record the revisions merged when you check in a merge result, you can find this information in Fisheye easily for the next merge operation.
- Subversion Changeset Parents and Branches
- SVN Authentication Issues — If multiple repositories have been defined in Fisheye for the same SVN Server and those repositories use different credentials, Fisheye may not use the correct credentials.
- What are Subversion root and tag branches?
- Why do I need to describe the branch and tag structure for Subversion repositories? — In Subversion, branches and tags are defined by convention, based on their path within a repository, and not directly defined by the repository. A few different layout alternatives are commonly used. It is also possible that you are using your own custom layout. As a result you need to describe to Fisheye which paths in your repository are used as branches and tags.
- Why don't all my tags show up in Fisheye?
Last modified on Oct 25, 2018
Powered by Confluence and Scroll Viewport.