This page last changed on May 05, 2008 by smaddox.
The first time you run a new version of FishEye, it will automatically upgrade its data. This may involve a complete re-index of your repository.
Before you start
- Before upgrading you should always read the Release Notes and Changelog for the version you are upgrading to, as well as any versions you are skipping.
FishEye 1.5 Upgrade Notes
- 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.
FishEye 1.4 Upgrade Notes
- If you were using the old Crowd Authenticator plugin in FishEye 1.3.x, you need to switch to the in-built Crowd Authenticator in FishEye 1.4+. Please see the Crowd documentation for details.
- As of version 1.3, FishEye requires a JVM version 1.5 or later. Previously, 1.4+ was required.
- Upgrading from 1.2.5 (or earlier) or 1.3beta8 (or earlier) will force a complete re-index of CVS repositories.
- Upgrading to this version will force a complete re-index of P4 repositories.
- Upgrading from from 1.1.x (or earlier) or 1.2beta2 (or earlier) will force a complete re-index of SVN repositories.
FishEye 1.3 Upgrade Notes
- As of version 1.3, FishEye requires a JVM version 1.5 or later. Previously, 1.4+ was required.
- Upgrading from 1.2.5 (or earlier) or 1.3beta8 (or earlier) will force a complete re-index of CVS repositories.
- Upgrading to this version will force a complete re-index of P4 repositories.
- Upgrading from from 1.1.x (or earlier) or 1.2beta2 (or earlier) will force a complete re-index of SVN repositories.
Upgrade Procedure
Your upgrade procedure depends on whether you are using a separate FISHEYE_INST directory. Read more about FISHEYE_INST in the Installation Guide.
Method 1: Using a Separate FISHEYE_INST Directory
- Extract the new FishEye version to a directory, leaving your FISHEYE_INST environment variable set to its existing location.
- Ensure that the FISHEYE_HOME environment variable, if set, points to your /NEW_FISHEYE/ directory.
- Start FishEye from the new installation.
- Follow any version-specific instructions found in the Release Notes.
Method 2: No Separate FISHEYE_INST Directory
You will need to copy some files from your old FishEye installation to your new one.
- Extract the new FishEye instance into a directory such as /NEW_FISHEYE/.
- Delete the /NEW_FISHEYE/var directory.
- Shut down the old FishEye instance if it is running.
- Copy /OLD_FISHEYE/config.xml to /NEW_FISHEYE/.
- Copy (or move) the /OLD_FISHEYE/var directory to /NEW_FISHEYE/var.
- If you have a Cenqua-issued FishEye license, copy your fisheye.license to /NEW_FISHEYE/. (Atlassian-issued licenses are included within config.xml.)
- Ensure that the FISHEYE_HOME environment variable, if set, points to your /NEW_FISHEYE/ directory.
- Start FishEye from the new installation.
- Follow any version-specific instructions found in the Release Notes.
|