Bamboo generic upgrade guide

はじめる前に

This upgrade guide contains generic upgrade tasks that are common across Bamboo versions. Please ensure that you also read the upgrade guide for the version you are upgrading to.

Bamboo 4.2 has been released. Read the Bamboo 4.2 Release Notes and Upgrade Guide.
Don't have Bamboo 4.2? Take a look at the features of Bamboo's latest major version and try it out!

Step 1. Identify your Bamboo directories

Click Administration, and then System Information in your Bamboo instance, and note the location of the 'Bamboo Home', 'Build Path' and 'Configuration Path' directories:

このページの内容

関連ページ

Step 2. Export Bamboo data

In Bamboo, export your Bamboo data for backup. See Exporting data for backup for instructions. Please note that this may take a long time to complete depending on the number of builds and tests in your system.

Step 3. Shut down Bamboo

Shut down Bamboo before performing the backup or upgrade steps below.

Step 4. Back up Bamboo

Back up your 'Bamboo Home' directory, which includes the builds and configuration directories, as identified in Step 1. For more information about these directories please see Important Directories and Files.
If you are using an external database, then use native database backup tools to acquire a database dump, as well.

Step 5. Re-install Bamboo

Make sure that your {BAMBOO_INSTALL} directory is either a new directory, or else delete your old {BAMBOO_INSTALL} directory before you begin, as legacy files may cause problems.
The {BAMBOO_HOME} directory must be different from the {BAMBOO_INSTALL} directory. This will ensure that your data is not lost when upgrading or re-installing Bamboo.

If you are installing using the .zip or .tgz packages:

Specify the {BAMBOO_HOME} directory in <Bamboo-install>/webapp/WEB-INF/classes/bamboo-init.properties, use the same 'Bamboo Home' directory as in your old installation. That is, specify the same directory and path as the 'Bamboo Home' directory shown in Step 1 (above).

If you are installing using the Windows installer or the Mac installer

Ensure that you then point the new installation to the old 'Bamboo Home', changing the path at file <Bamboo-install>/webapp/WEB-INF/classes/bamboo-init.properties. Note that in a EAR-WAR installation, the webapp directory may have a different name.

Follow Steps 1 and 2 of the installation instructions for your operating system:

Step 6. Update plugins

If you are using any plugins other than the ones that ship with Bamboo, check that each one is compatible with the new version of Bamboo. Upgrade any plugins that are out-of-date, and disable any plugins that are incompatible with your new version of Bamboo.

Step 7. Re-configure external user repositories

You only need to perform this step if either of the following apply:

LDAP integration — If you had previously integrated Bamboo with LDAP/AD, copy your old ../<Bamboo-install>/webapp/WEB-INF/classes/atlassian-user.xml to it's new location. Starting with version 3.2, the atlassian-user.xml file will be stored at {BAMBOO-HOME}/xml-data/configuration/. Please replace the existing file using your old atlassian-user.xml. Note that in a EAR-WAR installation, the webapp directory may have a different name.
Crowd integration — If you had previously integrated Bamboo with Crowd, you will need to re-enable Crowd integration. For details please see Integrating Crowd with Bamboo.

Step 8. Start Bamboo

Before you start Bamboo

Bamboo needs to have write access to your database to complete the upgrade tasks that will run when you start up Bamboo. Please consult your database documentation to ensure that you have configured your database appropriately.

Once you have installed Bamboo and set the bamboo.home property (as described in the Installation Guides), start Bamboo. The upgrade process will be performed when Bamboo starts up. You will not see the Setup Wizard.

Monitor the atlassian-bamboo.log to ensure that the upgrade process has completed successfully.

Step 9. Re-index Bamboo (if indicated in release notes)

Bamboo maintains an index of its build results. This allows Bamboo to display aggregate build results information across builds. You may need to perform a re-index of Bamboo if the upgrade process requires it. This step may or may not be required (depending on the upgrade versions). Also note that you only need to do this if you have existing data in Bamboo.

To re-index, go to Administration, then Indexing (under 'System').

Depending on the number of builds and tests you may have, the indexing process may take a significant amount of time. During this period, Bamboo will not be available. Also, it is advisable to ensure that all you have disabled all build queues (or all agents, if you are upgrading from Bamboo 2.0 or later), and that no builds are in progress when you start the re-indexing process. If you have a large instance, it is recommended that you reindex overnight.

Automatic upgrade of remote agents

For Bamboo 3.2 and later, remote agents are upgraded automatically. The remote agent can automatically detect when a new version is available, and has a special classloader that downloads the new classes from the server.

トラブルシューティング

If you have any problems during upgrade, please raise a support request at https://support.atlassian.com/ja/ and attach your atlassian-bamboo.log so we can help you find out what's gone wrong.

Child pages