Downloads (PDF, HTML & XML formats)
[FishEye Knowledge Base]
Documentation for FishEye 3.0.x. Documentation for other versions is available too.
Most upgrades (even major ones) do not require a reindex. If an upgrade is required, this will always be explicitly mentioned in the Upgrade Guide for that release.
To reindex a temporary copy of your FishEye instance:
config.xml
of your temporary FishEye instance to point to your temporary repository.FISHEYE_INST
directory.FISHEYE_INST/var/cache
directory on live FishEye with the FISHEYE_INST/var/cache
from your test server.To make a copy of your FishEye instance, follow the instructions for Migrating FishEye Between Servers.
To make a copy of your repository use rsync (for CVS repositories in the Linux environment) or svnsync documentation (for Subversion only).
If you need to reindex your repository on your production system but don't want to burden your production server, carry out the following steps:
1. Install another instance of FishEye on a test server (the same FishEye version as the one you are using).
2. Add a repository to FishEye with the exact same name and details as that referenced by the production server.
3. Let it finish indexing. Go to Administration > View Repository List > Stop (shown next to the name of your repository) and disable on both production and test.
4. Copy over the FISHEYE_INST/var/cache/REPO
directory on the production FishEye with the FISHEYE_INST/var/cache/REPO
directory from the test server.
5. Trigger a review revision data re-index: Administration > Repository > Maintenance > Review-Revision Data Index.
For this procedure, neither server needs to be shut down.
1 Comment
Keith Lee
/var/cache/REPO/fe_clone.properties seems to be modified if repository source is different