This documentation relates to an earlier version of FishEye.
View

Unknown macro: {spacejump}

or visit the current documentation home.

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.

(info) 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,

  1. Open the 'Admin Menu', by clicking the 'Administration' link in the footer of any FishEye page.
  2. 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.
  3. Select one of the re-indexing options discussed below.
  4. 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.

(info) 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 access indexing functions for a repository,

  1. Click the menu labelled with your user name in the the FishEye/Crucible header, and click the 'Administration' option. You will need to be logged in as an administrator to see this link. The FishEye/Crucible administration console will be displayed.
  2. Click the 'Repositories' link. The list of repositories set up in your FishEye instance will be displayed.
  3. Click the name of the repository, (under the 'Name' column in the list of repositories). The Repository Options for the repository will be displayed in a dialogue.
  4. Click the 'Maintenance' tab. Indexing information for the repository will be displayed as well as indexing functions (see screenshot below).
    • 'Repository Source Index':
      • Click the 'Start' button next to 'Scan for Updates' to 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.
      • Click the 'Start' button next to 'Re-index' to delete the current cache and re-index the repository from the beginning. This action will also restart the repository.
    • 'Review-Revision Data Index' — (applies only when using Crucible with FishEye) Click the 'Start' button next to 'Re-index' to re-index all the Crucible review data associated with the current repository.
    • 'Line Count Data Index' — Click the 'Start' button next to 'Re-index' to 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.
    • 'Subversion Non-Version Properties (revprops)' — (Subversion repositories only) Set the revision numbers to scan from and to, and click the 'Start' button next to 'Re-index' to 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.

Screenshot: FishEye Index Maintenance menu
  • No labels



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.