Index![]()
Downloads (PDF, HTML & XML formats)
[Bamboo Knowledge Base Home]
Documentation for Bamboo 4.0.x. Documentation for earlier versions of Bamboo is available too. 
![]()
The instructions on this page describe how to upgrade to Bamboo 3.1 from a previous version of Bamboo. For details on the Bamboo 3.1 release, see the Bamboo 3.1 Release Notes.
Please follow the Bamboo 3.1-specific instructions on this page, in addition to the upgrade instructions in the Bamboo generic upgrade guide.
Please read the Supported platforms page for the full list of supported platforms for Bamboo.
On this page:
We have changed the default behaviour of the SVNKit library in Bamboo. As a result, any source code checked out by Bamboo will be automatically upgraded to be compatible with Subversion 1.6. This does not adversely affect any pre-1.6 Subversion servers. However, if you use a pre-1.6 Subversion client to access code checked out by Bamboo, then any Bamboo builds on that code may fail.
If you want to prevent any checked out code from being automatically upgraded to SVN client format 1.6, you will need to run Bamboo with the following system property:
-Dbamboo.svn.wc.format=1.5
For more information, please see this FAQ: How do I manually set the version of new Subversion workspaces.
We are ending support for Java Platform 5 (JDK/JRE 1.5) in this release. Please see End of Support Announcements for Bamboo for further details.
The introduction of the Tasks feature in Bamboo 3.1 means that the following activities will occur during the upgrade to Bamboo 3.1:
If you are using the Bamboo distribution (not EAR-WAR) for Windows, please note that the location of the following files/directories have changed.
%USERPROFILE%\bamboo.log, rather than in the logs folder of your installation directory. For Bamboo running as a Windows service, log files are located at %WINDIR%\System32\Config\systemprofile\bamboo.log. Note, existing logs will not be migrated, however new logs will be written to the new location when running Bamboo after the upgrade.%WINDIR%\Temp, rather than in the user's temporary directory.The new Gravatar support feature is enabled by default in Bamboo 3.1. For more information, see Configuring Gravatar support.
Before you begin, do the following:
We strongly recommend that you do the following to back up your Bamboo installation:
If you are using plugins, ensure that your plugins are compiled against 3.1 before upgrading.
Before you upgrade, please read the following important points that relate to Bamboo 3.0.
In addition to the notes below, please read the Upgrade Guide for every version you are skipping during the upgrade. The complete list of Upgrade Guides is available here.
If you are a Bamboo plugin developer, please refer to our Changes for Bamboo 3.1 guide, which outlines changes in Bamboo 3.1 that may affect Bamboo plugins compiled for Bamboo version 3.0.x or earlier.
If something is not working correctly after you have completed the steps above to upgrade your Bamboo installation, please check for known Bamboo issues and try troubleshooting your upgrade as described below:
5 Comments
David Corley
May 25, 2011We're planning an upgrade from 2.6.3 to 3.1.x. Is the phased 2.6->2.7->3.1 upgrade strictly necessary?
We've already carried out a test phased upgrade, and we've got a good handle on the time needed.
Is is possible to upgrade directly from 2.6.x to 3.1.x ?
roy_lyons
Jun 01, 2011I would be interested in the timings you experienced - we are planning to move from 2.4.2 to 3.1.1 -- just about to start testing and gathering data for the time it will take...
Renan Battaglin
Jun 03, 2011Hi David,
Yes, we still believe that upgrading 2.6 -> 2.7 -> 3.1 is the safer method. A 2.6 -> 3.1 upgrade may work, but depending on the DB data and size of the instance, some of the Upgrade Tasks may fail.
Cheers,
Renan Battaglin
Atlassian Support
Anonymous
Sept 14, 2011Does this mean, I can skip 3.0 upgrade?
we have 2.7.1 and planning on upgrading to 3.1.
My upgrade plan was upgrading to 3.0 first and upgrading to 3.1?
Rob Banfield
Jul 12, 2011Spent an afternoon on this, for any remote notes where you use
Make sure each agent gets this and not just the server.