SVN Repository Reports Incorrect Number of Committers
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
After creating an SVN repository in Fisheye and starting indexing the repository, the initial indexing process is stopped with the following log message:
1
2
3
INFO [IncrementalPinger1 Repo_Name] fisheye.app DiffChangeSetProcessor-processFileRevisions - Creating changeset XXXXXX
WARN [IncrementalPinger1 Repo_Name] fisheye.app DefaultLicenseEnforcer-validateCommitterLimit - Committer limit exceeded - committer list: user1, user2, user3, user4, user5, user6, user7, user8, user9, user10, user11
WARN [IncrementalPinger1 Repo_Name] fisheye.app BaseRepositoryScanner-setLicensePolicyReached - License limit reachedFisheye will list in the log message the names of all the committers detected until that revision in the repository. In the message above: user1, user2, user3,... . String XXXXXX represents the last revision created before Fisheye was able to detect the 11th committer in the repository.
Cause
Starter Licenses for Fisheye/Crucible limit the total number of committers to 10 and repositories to 5. In this case, more than 10 SVN users committed code to the repository and were detected by Fisheye.
Resolution
The purpose is to have a maximum of 10 users visible to Fisheye by allowing the application to see code commits for a maximum of 10 users. This can be achieved in two different ways:
Make invisible to the repository the paths in
/trunk,/branchesand/tagsthat contain code committed by the exceeding users. This can be done using the "Exclude Feature".Use the repository "Start Revision" setting to define an indexing starting point. This would allow the repository to be able to see only the range of changesets that have 10 or less users.
In order to determine the changeset number to add to the Start Revision field, the following command can be run to see what was the last user commit:
1
svn log https://svn.your_repo.com | sed -n '/username/,/-----$/ p'"https://svn.your_repo.com" is the SVN Server where the repository is located.
"username" is the user to be made invisible to Fisheye.
Was this helpful?