Mapping Users, Indexing, Starter license

Hi there,

I have a starter licence for Fisheye. We're working on an existing code repository which has some old users who aren't with our group any more. When I try to index the repository and map the older user IDs to the current commiters it seems that the system still doesn't allow me to finish indexing the repository even though the tech notes seem to indicate that will work.

Any ideas? We've got a Subversion repository and yes I've tried re-indexing twice.



The tech notes state:

Reconfigure your repository

This option lets you configure your repository to remain within the limits of the Starter License. You can take the following actions to reduce the scope of FishEye's indexing:

  1. Change the repository definition to look at a subset of your repository
    Typically this involves setting the path within your repository that you wish FishEye to index. Read more.
  2. Exclude parts of the repository
    You can exclude portions of your repository that you are not interested in. Committers that are active in only these areas will not appear in FishEye and not be included in the committer count. Read more.
  3. Set a starting point
    Some of the FishEye SCM integrations allow you to configure a starting revision from which to start indexing. All commits prior to this starting point are not included in FishEye and do not contribute to the committer count. Read more.
  4. Map Committers
    If your developers have not correctly configured their committer names for Git or Mercurial, they may have committed with multiple identities. It is then possible to remap these to correct the problem. See the knowledge base article, Git or Hg Repository exceeds number of allowed Committers

Once you have reconfigured your repository, you will need to re-index the repository, allowing you to remain under the limits of the Starter license.

I chose option 4 ... which should allow me to continue right??

1 answer

0 votes

Option 4 only applies to Git and Mercurial repositories. Note that "mapping" in this instance refers to mapping done in the SCM itself and not FishEye's user-mapping feature (which maps users to committers).

I suggest you use option #3 for Subversion repositories.

Why isn't there the same ability for Subversion?

The mapping in option 4 is done in the repository level according to the KB. Subversion repository does not have this function.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Jan 15, 2019 in Statuspage

Introducing Statuspage Getting Started guides! First up: What is Statuspage?

Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...

266 views 4 2
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you