[FishEye ナレッジ ベース]
You can manually perform a number of indexing functions on your repositories in FishEye.
Note, an indexing scan for a repository can take hours or possibly days, depending on the size of the repository, network speed, machine performance and other factors.
To access indexing functions for a repository:Click Maintenance in the left-hand panel.
Choose from the following indexing options:
Repository Source Index | |
Run Incremental Index | If the repository has already been indexed, this will start 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. |
再インデックス化 | Delete the existing cache and re-index the repository from scratch. For large or slow repositories this may take some time, during which some functionality will be unavailable. This action will also restart the repository. |
Review-Revision Data Index | (Crucible only) Re-index all the Crucible review data associated with the current repository. |
Line Count Data Index | 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. |
Changeset Discussion Index | Re-index the changeset discussion index, which is used to display changeset discussions in activity streams. |
Subversion Non-Version Properties (revprops) | (Subversion repositories only) Re-scan the non-versioned properties of the repository (e.g. check-in comments if so enabled) and amend the entry in FishEye and Crucible accordingly. Set the revision numbers to scan from and to. 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. |