This page last changed on Oct 19, 2009 by edawson.
This page contains instructions on how to re-index your repository in FishEye.
Re-indexing involves FishEye doing an intensive scan of the repository contents, so it can quickly show the repository data via FishEye's web interface. Re-indexing may be required in a number of situations such as server maintenance, changes in your repository, major setting changes and upgrades to FishEye.
Due to the complexity of SCM repositories, an indexing scan may take many hours or even days to complete. During this time, your FishEye users may be inconvenienced as they will not by able to view the repository being indexed. As a result, Crucible users will not be able to carry out reviews unless you have Crucible set to store all revisions offline.
Performing a Manual Re-index
To re-index your repository,
- Open the 'Admin Menu', by clicking the 'Administration' link in the footer of any FishEye page.
- The 'Repository List' screen opens by default. In the main window, the list of configured repositories is shown. Click 'View' next to the desired repository, then click on maintenance.
- Select one of the re-indexing options discussed below.
- The repository will be re-scanned, a process that may take hours or possibly days, depending on the size of the repository, network speed, machine performance and other factors.
How do I mitigate long re-index times when upgrading? See the FAQ page on this topic.
Indexing Settings
Settings and administrative operations for repository indexing are located on the Indexer page.
To get to this page, go to 'Administration' > 'Repository List' > 'View' (next to your repository name) > 'Indexer' > 'Maintenance'
The 'Indexer Maintenance' screen opens, where an administrator can manually trigger the following actions:
Action |
Description |
Refresh |
Refreshes the status string, in the Status box. This will show the name of any repository task that FishEye is currently carrying out (if any). This may be helpful to monitor the progress of an initial indexing task or to diagnose problems (such as your repository server being out of action). |
Re-index Repository |
Delete the current cache and re-index the repository from the beginning. This action will also restart the repository. |
Re-index Crucible Data |
(applies only when using Crucible with FishEye) Re-index all the Crucible review data associated with the current repository. |
Re-index Linecount Data |
Re-index the linecount data used to generate the LOC (Lines Of Code) charts. The linecount data will be recalculated in daily buckets based on the server timezone. |
Scan Now |
Run a repository scan (also referred to as indexing) now. If the repository has already been indexed, it will be an incremental scan, otherwise an "initial" scan. This is especially useful if you have not set the repository to poll automatically, or it is set with a long poll (interval) period. |
Rescan Revisions |
For a Subversion repository, you can rescan non versioned properties (revprops). In Subversion it is possible to enable non-versioned properties (e.g. the check-in comments) to be updated by committers. When this happens, FishEye will not automatically pick up the updates. By rescanning specific revisions, FishEye will rescan the non-versioned properties and amend the entry in FishEye accordingly.
For a Perforce, repository, you can rescan changelists. This will rescan changelist metadata (author, date, commit message) and any job fixes associated with changelists in the the given changelist range. |
Screenshot: FishEye Index Maintenance menu

|