Upgrading Bamboo Data Center
This guide applies to Bamboo Data Center running in a cluster. Upgrading Bamboo to the next version will incur a downtime.
1. Check upgrade requirements
Make sure your environment meets the minimum requirements to run the desired version of Bamboo Data Center. To ensure your instance works correctly after the upgrade, see the latest End of support announcements.
You can update any version of Bamboo Data Center to the latest version, as there is no required upgrade path.
Learn more about migrating to Bamboo Data Center
If you're planning to migrate from Bamboo Server to Bamboo Data Center, remember to:
Check the infrastructure and hardware requirements described in Clustering with Bamboo Data Center.
Go to Administration> Troubleshooting and support tools, then review the Log analyzer for any issues that may need to be resolved.
Check the compatibility of your apps with the version of Bamboo Data Center you plan to upgrade to.
Go to Administration> Manage apps > Bamboo update check.
Select the version you plan to upgrade to, then select Check.If your apps are incompatible
If your users rely on particular apps, you may want to wait until the apps are compatible with the desired version of Bamboo Data Center.
- Make sure that all important builds are finished before the upgrade. A new Bamboo Data Center version might not be able to process old build results or complete the old builds successfully.
3. Upgrade in a test environment
Before you upgrade Bamboo Data Center to the next major or minor version, perform the upgrade in a test environment first:
Follow the upgrade steps below.
If possible, test any unsupported apps, customizations, and proxy configuration.
Upgrade Bamboo Data Center
The installation path is referred to as
<bamboo-install> and points to the directory into which you extracted the Bamboo Data Center package. It's different from
<bamboo-shared-home>, which both point to the directories where data is stored.
Before you upgrade, you need to stop all the nodes in the cluster. Start with all your non-primary nodes, so they won’t try to take over after you stop the primary node.
If you run Bamboo as a Windows service, uninstall the service by using the
UninstallService.bat executable from Bamboo binaries.
Configure your load balancer to redirect the traffic away from Bamboo until the upgrade is complete on all nodes. Your router settings shouldn't allow agents and user traffic until all nodes are updated and confirmed operational.
2. Back up your data
Export your database
Use native database tools to create a backup. For more information about external databases, see Connect Bamboo to an external database.
Back up your configuration
Create a backup for <bamboo-home> directories from each node as well as the
<bamboo-shared-home> directory. At the bare minimum, you should back up:
<bamboo-home>on each node.
all content of the
3. Download Bamboo Data Center
Download the appropriate file for your operating system from our software download page.
A. Install a new instance
To upgrade, you need to install a new Bamboo Data Center instance in a
<bamboo-install> directory that's different from the original instance's installation directory.
Before you start the new installation, make sure the original instance isn't running.
To prevent data loss during updates or reinstallation, the
<bamboo-install>directory must be different from the
B. Configure the new instance
Set home directories
<bamboo-shared-home> to use the same paths as the original Bamboo instance:
Go to the new instance's
bamboo.homevariable to use the
<bamboo-home>path of the original instance
bamboo.shared.homevariable to use the
<bamboo-shared-home>path of the original instance
Install a JDBC driver
If the JDBC driver for your database isn't bundled with Bamboo, you need to install it for the new Bamboo instance yourself. See Connect Bamboo to an external database for detailed instructions.
Migrate the existing configurations to your new Bamboo installation
If you've modified any properties in the configuration files of your existing Bamboo installation, make the same modifications in your new installation. Note that you can't simply copy the configuration files from the existing installation and replace the equivalent files in your new installation, because the properties in the configuration files may have changed between versions.
For each file you've modified in your existing Bamboo installation, you need to manually edit each equivalent file in your new Bamboo installation and re-apply your modifications.
The table below lists the most commonly modified files and their locations within your Bamboo installation directory.
Location in Bamboo installation
setenv.bat (Windows) または setenv.sh (Linux)
Modified if you had integrated Bamboo with Crowd
Check database access permission
Before you start the new Bamboo instance, make sure that it has the write access to the database, which is required to complete the upgrade tasks.
C. Start Bamboo
Start the new Bamboo instance and wait for the upgrade to finish. You can check whether the upgrade was successful in the
Don’t reconfigure your load balancer yet. Traffic to Bamboo should be restored only after all nodes are updated and confirmed operational.
Upgrading Bamboo may require reindexing. Depending on the number of existing builds and tests, the reindexing process may take a significant amount of time, during which Bamboo won't be available.
D. Update any installed apps
If you installed any apps in addition to the pre-installed system apps:
Check if all apps are compatible with the new version of Bamboo.
Update any apps that are out of date.
Disable any apps that are incompatible with the new version of Bamboo.
5. Install Bamboo on remaining nodes
The next step is replicating your upgraded Bamboo directories to other nodes in the cluster.
Stop Bamboo on the first node.
Install the new Bamboo version on the next node the same way you did on the first node.
Make sure to use
<bamboo-shared-home>specific to the node.
You don’t need to update installed apps again.
You can copy any modified configuration files from the first node.
Start Bamboo and confirm that everything works as expected.
Stop Bamboo on this node before continuing with the next node.
6. Start Bamboo
Once all nodes have been upgraded, you can start Bamboo Data Center on each node, one at a time. Then, restore your load balancer configuration to direct agents and user traffic to Bamboo.
Automatic update of remote agents
Most of the time, remote agents are updated automatically. Remote agents detect when a new version is available and download new classes from the server.
For more information, see Bamboo remote agent installation guide.
If you followed the documentation and still experience problems with the upgrade process:
Check the How to upgrade/migrate Bamboo article in the Bamboo Knowledge Base.
Ask questions at https://answers.atlassian.com.
Create a support ticket. To help us address the issue, attach the
atlassian-bamboo.logfile to the ticket.