Unable to start review for a Git branch

[Thomas Hauk]

After purchasing 10-user licences for both Crucible and FishEye, I am unable to start a review for a branch in my Git repository.

The Git repo is a repo created with git-tfs bridge running on a Windows PC. When I was using the evaluation licence, everything worked correctly.

Problem #1: After upgrading to 3.4.4, the repository (as listed in Crucible) was "Stopped". It couldn't be "Started" until a re-indexing was done; but I couldn't re-index because it was "Stopped". This is a fine Catch-22. I resolved it by forcing a full re-clone and re-index.

Problem #2: The re-indexing did not finish because the Git repo contains commits from more than 10 people. (see image below)

Problem #3: The following header appeared at the top of my browser page. The "Evaluate, Upgrade or Reconfigure your repository" link, which is the shortened URL confluence.atlassian.com/x/3IIfD, does not work.

Problem #4: It is not clear what the problem is or how I would resolve it by "reconfiguring" my repository.

Problem #5: The branch on which I would like to start a review does not appear in the list of branches when I create a new review; when I manually enter the branch name instead of "master", the message "No matching changesets" is displayed.

How do I fix these issues?

[gustavo_refosco]

Hi Thomas,

Please take a look at https://confluence.atlassian.com/display/FISHKB/Git+or+Hg+Repository+exceeds+number+of+allowed+Committersfor a workaround for this issue. As described by it, one of the easier solutions is to use the .mailmap file.

For the link that is not working I've created a bug report you can see at https://jira.atlassian.com/browse/FE-5233. Please feel free adding any comments to it as well as voting to create it's popularity and likelihood of being implemented in a future release.

For more information on how Atlassian implements new features and improvements please see the following document: http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy

Regards,
Gustavo Refosco
Atlassian Support