Adding CVS Module In JIRA Fails With Error 'Error parsing cvs log: Invalid branch revision'
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Symptoms
JIRA throws error 'Error parsing cvs log: Invalid branch revision' when CVS module is added.
The following appears in the atlassian-jira.log:
1
2
3
4
5
2012-10-05 15:14:10,511 http-443-6 ERROR admin 914x87914x1 admin 10.64.1.142 /secure/admin/AddRepository.jspa [action.admin.vcs.AddRepository] Error occured while parsing cvs log.
net.sf.statcvs.input.LogSyntaxException: Invalid branch revision:0.1
at net.sf.statcvs.input.BranchData.calculateRevisionNumbers(BranchData.java:56)
at net.sf.statcvs.input.BranchData.<init>(BranchData.java:35)
at net.sf.statcvs.input.CvsFileBlockParser.parseSymbolicNames(CvsFileBlockParser.java:196)Diagnosis
Check if there any tag that is referring to the non-existence revision number. The step below can be use:
Run the following command to create a rlog.log file for the CVS module in question. This creates a file similar to the file that JIRA parses:
1cvs rlog <module> > rlog.logDo a search in the rlog.log file for all the occurrences of the branch revision in question (the number that JIRA reported when attempt to add CVS module is made).
check for the non-existance revision. In this example, the reported a problem revision is 0.1. So , use a text editor (e.g. Notepad++) to find all the occurrences of " 0.1" (used a space in front to find only those relevant). Examine each search hit.
Cause
By default, CVS revision number start with 1.1. So, any number lower than 1.1 is invalid.
Solution
Resolution
Repair the CVS module by referring the tag to it's valid revision of the file by using the following CVS command on all the relevant files. It's better to contact and consult the CVS administrator to repair the module. The example command that can be use is:
1cvs tag -r <revision> <tag> <file>Add CVS module to JIRA
Was this helpful?