Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,367,588
Community Members
 
Community Events
168
Community Groups

Exceeding committer limit with starter license due to temporary misconfigured git user configurations

We have a fisheye starter license for our small team of six developers. Since multiple of our developers had their git configuration incorrect for some time (i.e. their mail addresses were wrong causing the commits to appear to be from different users) we are now reaching Fisheye's limit of ten committers causing the initial indexing of the repository to stop. I was hoping that this could be solved using the user mappings, but apparently that does not change it.

Is there anything we can do aside from buying the next license level? Maybe manually change files in the repository to exchange the wrong git usernames with the correct ones?

Best regards,

Arne Bergmann

3 answers

1 accepted

1 vote
Answer accepted

There are a few solutions offered in Restrictions on FishEye Starter Licenses.
The two most practical are to set a start revision (very simple to do, but you'll miss part of the history in FishEye), and to map committers.
This is described in the Git or Hg Repository exceeds number of allowed Committers Knowledge Base article.
Although you can rewrite history, it's much simpler to use a .mailmap to map the incorrect old email addresses to the correct ones.

Please, provide a solution to map committers also for Subversion.

Its 2016 and no solution for this? We have 50+ developers in our Mercurial repository history but less that 10 active today.  Rewriting the history log is just out of the question. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events