FishEye 2.9 upgrade guide

Below are some important notes on upgrading to FishEye 2.9. For details of the new features and improvements in this release, please read the FishEye 2.9 release notes.

Upgrade notes

FishEye 2.9

  • The JDBC driver for MySQL is no longer bundled with FishEye/Crucible – Due to license restrictions the MySQL JDBC driver cannot be bundled with FishEye/Crucible. Please download the driver from http://dev.mysql.com/downloads/connector/j/ and install it to the FISHEYE_INST/lib directory. For more information see Migrating to MySQL.
  • The Connection pool manager has changed — FishEye and Crucible now use the BoneCP connection pool manager instead of the third-party c3p0 library previously used in FishEye/Crucible 2.8 and earlier versions. The BoneCP connection pool manager has been preconfigured in FishEye and Crucible to work out-of-the-box for most customers. Read Configuring the database connection pool for a description of the default settings and for instructions on how to override them.
  • The 'Suggest Reviews' function has been removed from Crucible — From this release onwards, a Crucible user will no longer be prompted to add to an existing review when creating a review from a changeset. We have removed this functionality based on user feedback that it was confusing and not being used. This allows users who want to add changesets to an existing review to simply navigate to that review and use the 'Add Content' option. Users can also add commits to an existing review via commit messages. Removing 'Suggest Reviews' also improves performance when creating reviews, as Crucible does not have to search for and suggest reviews.
  • Remote API is now permanently enabled — From this release of FishEye and Crucible onwards, the 'Remote API' setting in 'Server Settings' will not be configurable. The remote API is now always turned on, to make integration with JIRA and other services more straightforward.

On this page:

Related pages:

Upgrade procedure

Before you begin

  • Test your upgrades in your test environment before rolling into production.
  • Back up your entire FishEye instance (see Backing up and restoring FishEye data):
    • If you are backing up your FishEye instance using 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.

If you are already running a version of FishEye, please follow the instructions in the general 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 Atlassian finds out about a problem with the latest version of FishEye after the software is released. In such cases we publish information about the known issues in the FishEye Knowledge Base. Please check the FishEye 2.8 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.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport