This page last changed on Feb 09, 2011 by alui.
This page describes the recommended method of upgrading to a new version of FishEye.
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.
On this page:
Before You Start
- Back up your entire FishEye instance (see Backing Up and Restoring FishEye Data), i.e.
- If you are backing up your FishEye instance via the Admin interface, tick all of the 'Include' checkboxes (e.g. repository and application caches, plugins and their configuration data, SQL database, etc).
- If you are backing up your FishEye instance using the command-line interface, do not use any exclusion options.
- Read the Release Notes and Changelog and version-specific Upgrade Guide for the version you are upgrading to, as well as any versions you are skipping.
- Check the Supported Platforms to ensure that your system meets the requirements for the new version.
- Check for known issues in the FishEye Knowledge Base.
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
- Shut down your existing FishEye server.
- Make a backup of your FISHEYE_INST directory.
- Extract the new FishEye version to a directory, leaving your FISHEYE_INST environment variable set to its existing location.
- 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 and /NEW_FISHEYE/cache directories.
- 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.
- Copy (or move) the /OLD_FISHEYE/cache directory to /NEW_FISHEYE/cache.
- If you have a Cenqua-issued FishEye license, copy your fisheye.license to /NEW_FISHEYE/. (Atlassian-issued licenses are included within config.xml.)
- Start FishEye from the new installation.
- Follow any version-specific instructions found in the Release Notes.
Method 3 - Without a FISHEYE_INST Directory, but would like to set one up
- Shut down the old FishEye instance if it is running.
- Set up the FISHEYE_INST environment variable, then create the FISHEYE_INST directory on your filesystem.
- Copy the /OLD_FISHEYE/config.xml to /FISHEYE_INST.
- Copy the /OLD_FISHEYE/var directory to /FISHEYE_INST.
- Copy the /OLD_FISHEYE/cache directory to /FISHEYE_INST.
- Extract the new Fisheye archive into a directory such as /NEW_FISHEYE/.
- Start Fisheye from the new installation by running NEW_FISHEYE/bin/run.sh. (Use run.bat on Windows).
- If you configuration is not automatically picked up and you cannot see your existing repositories, check your Administration > Sys-Info page, where you will see information about FISHEYE_HOME and FISHEYE_INST. Check your FISHEYE_INST is pointing to the right directory.
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 2.4 Known Issues in the FishEye Knowledge Base 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.
|