On this page:
- Per-Author Line Counts require the 'Store Diff' setting to be true, but this will be false for existing repositories. Existing repositories will require this setting to be changed to 'true', then a full re-scan of that repository must be done. This is not essential to continue using your FishEye instance — it is only required for per-author graphs on the FishEye chart page.
- Upgrading from 1.2.5 (or earlier) or 1.3beta8 (or earlier) will force a complete re-scan of CVS repositories.
- Upgrading to this version will force a complete re-scan of P4 repositories.
- Upgrading from from 1.1.x (or earlier) or 1.2beta2 (or earlier) will force a complete re-scan of SVN repositories.
Upgrade a test environment first
As always, please test your upgrades in your test environment before rolling into production.
If you are already running a version of FishEye, please follow these instructions on FishEye upgrade guide.
Checking for Known Issues and Troubleshooting the FishEye Upgrade
If something is not working correctly after you have completed the steps above to upgrade your FishEye installation, please check for known FishEye issues and try troubleshooting your upgrade as described below:
- Check for known issues. Sometimes we find out about a problem with the latest version of FishEye after we have released the software. In such cases we publish information about the known issues in the FishEye Knowledge Base. Please check the FishEye Knowledge Base for known issues and follow the instructions to apply any necessary patches if necessary.
- Did you encounter a problem during the FishEye upgrade? Please refer to the guide to troubleshooting upgrades in the FishEye Knowledge Base.
- If you encounter a problem during the upgrade and cannot solve it, please create a support ticket and one of our support engineers will help you.