Restrictions on Fisheye Starter Licenses
This page explains the limitations of the Fisheye Starter license and provides general information about using this license in production.
On this page:
What is a Starter License?
Starter licenses are low-cost licenses that allow small teams to make use of Atlassian products (see more information ). Fisheye Starter licenses were introduced with the release of Fisheye 2.0.5 (October 2009).
What are the Starter License restrictions?
Fisheye Starter Licenses are restricted to no more than:
See Fisheye Licensing and Purchasing for more details.
Note that all other Fisheye licenses support unlimited repositories and unlimited committers per repository.
What happens if I exceed the Starter License limits?
If you have more than 5 user accounts in Fisheye, your users will not be able to log in to Fisheye until an administrator reduces the number of user accounts.
If you have more than five repositories, Fisheye will prevent more than five repositories from being enabled at any given time. Administrators can control which five repositories are enabled.
NOTE: This repository, <repository-name> has more than 10 committers which exceeds the limits for your Starter license. Indexing has stopped. To fix this, you can Evaluate, Upgrade or Reconfigure your repository.
The links in this warning will lead you to the following solutions:
30-day evaluation licenses are available to allow you to try out Fisheye and other Atlassian products. You can select a license that allows more users than your current license.
You can upgrade your license at any time (via the Atlassian online store), which will remove the committer and repository limits which apply to the Starter License. Please ensure to restart your repository, after the license upgrade, to ensure the changes are picked up for the new committer limit.
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:
- 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.
- 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.
- 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.
- 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.
Frequently Asked Questions
What happens when the 11th unique committer is encountered during indexing?
For all SCMs other than CVS Fisheye will index all revisions up to but not including the revision that introduced the 11th committer. Since CVS is indexing is file-by-file based, Fisheye will index files until it reaches the committer limit. Remaining files in the repository are not indexed. This means only files which have been indexed will be displayed in changesets and changesets may be incomplete.
What happens when a Fisheye instance with a Starter license is started, using existing indexes with more than five repositories?
Fisheye will only start indexing on the first five repositories. An administrator can use admin UI to adjust which repositories are enabled and hence control the five repositories that are started. Fisheye should then be restarted.
What happens when a Fisheye instance with a Starter license is started, using existing indexes with one or more repositories with more than ten committers?
Fisheye will display all information currently indexed but for each repository that has reached the ten committer limit, no further revisions will be indexed.
What happens on upgrade from a Starter license, if indexing has been paused due to the committer limit being reached?
On restart of Fisheye, indexing will resume for all repositories. Each repository can restarted individually to avoid restarting Fisheye. Due to the nature of CVS indexing, we recommend reindexing any CVS repositories which have reached the committer limit prior to the license upgrade.
What happens when upgrading from a Starter license, when repositories have not started due to the repository limit being reached?
On restart of Fisheye, all enabled repositories will start. Each repository can restarted individually to avoid restarting Fisheye.
What happens if my evaluation license has expired and I upgrade to a Starter license, however I have exceeded the Starter license limitations?
As described above, a maximum of five repositories will start and for any repository with more than 10 committers, no further indexing will occur. All existing indexed content is retained and can be viewed.
What happens when downgrading to a Starter license, where the repository limit has been exceeded?
A maximum of five of your configured repositories will start running. The remainder will not start but will continue to be available.
What happens when downgrading to a Starter license, where the committer limit has been exceeded for one or more repositories?
No further indexing will occur for the repositories where the