Attempting to Insert a Revision which Already Exists
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
Symptoms
When indexing a repository, the following error can be seen in the logs:
1
2
2012-12-07 16:09:09,646 ERROR [InitialPinger1 repository] fisheye DiffChangeSetProcessor-insertNewRevision - Attempting to insert a revison which already exists for acme/tnt.java@666
Cause
There are two possible causes:
An incorrect SVN tag and branch structure has been applied to the repository.
Fisheye is indexing paths that are not part of the repository.
Resolution
Change the SVN tag and branch settings in order to match the repository structure. Use the instructions on the following page to verify SVN symbolic rules.
Exclude the paths that are not part of the repository from being indexed.
Was this helpful?