Skip to end of metadata
Go to start of metadata

The instructions on this page describe how to upgrade to Bamboo 4.0 from a previous version of Bamboo. For details on the Bamboo 4.0 release, see the Bamboo 4.0 Release Notes.

Please follow the Bamboo 4.0-specific instructions on this page, in addition to the upgrade instructions in the Bamboo upgrade guide.

Please read the Supported platforms page for the full list of supported platforms for Bamboo.

On this page:

Upgrade Notes

The following upgrade notes are specific to Bamboo 4.0

  • Bamboo's deprecated Remote API has been removed. If you are using this API, migrate to the Bamboo REST API.
  • There are no major schema upgrade tasks that may cause the Bamboo upgrade from 3.4 to 4.0 to take an extended amount of time.
  • If you are using Elastic Bamboo, we've upgraded JDK6, Grails 1.2, Grails 1.3 and Maven 3 to the latest minor releases on the stock images. Additionally, we've added Grails 2.0 to the image. See here for a complete list of elastic image contents.

Upgrading from Bamboo 3.4 to 4.0

To upgrade to Bamboo 4.0, following the appropriate instructions below:

We strongly recommend that you back up your Bamboo instance and database before upgrading, as described in the Bamboo upgrade guide.

Upgrading from Bamboo prior to 3.4

In addition to the notes below, please read the Upgrade Guide for every version you are skipping during the upgrade. 

Notes for upgrading from Bamboo 3.2

Notes for upgrading from a version of Bamboo prior to 2.7.4

  • You will need to upgrade to Bamboo 2.7.4 before upgrading to Bamboo 4.0. If you are using a version of Bamboo earlier than 2.6.3, we recommend that you upgrade to 2.6.3 before upgrading to Bamboo 2.7.4. Bamboo 2.6.3 can be downloaded from the Bamboo Archived Downloads page. Bamboo 2.7.x introduces a number of significant and irreversible changes, so a phased upgrade is recommended. Please see the Bamboo 2.7.x Upgrade Guide for more details.
  • You will need to set aside time, as described in the Bamboo 2.7.x Upgrade Guide, for Bamboo to migrate existing Plans to the new Plan structure in Bamboo 2.7.4.
  • If you are upgrading from Bamboo 2.5 or earlier, you will need to set aside time, as described in the Bamboo 2.6 Upgrade Guide for Bamboo to migrate its test result data (stored in XML files on the filesystem) into the database.
  • If you are upgrading from a version of Bamboo prior to 2.0, you must upgrade to Bamboo 2.0.6 first before upgrading to Bamboo 2.6.3 ( and then 2.7.4). Please read the Bamboo 2.0 Upgrade Guide for important upgrade instructions for upgrading from earlier versions of Bamboo.

Developing for Bamboo 4.0

If you are a Bamboo plugin developer, please refer to our Changes for Bamboo 4.0 guide, which outlines changes in Bamboo 4.0 that may affect Bamboo plugins compiled for earlier versions of Bamboo.

Checking for Known Issues and Troubleshooting the Bamboo Upgrade

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:

  • Check for known issues. Sometimes we find out about a problem with the latest version of Bamboo after we have released the software. In such cases we publish information about the known issues in the Bamboo Knowledge Base. Please check the Bamboo Known Issues in the Bamboo Knowledge Base and follow the instructions to apply any necessary patches if necessary.
  • Did you encounter a problem during the Bamboo upgrade? Please refer to the guide to troubleshooting upgrades in the Bamboo 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.


  1. Are there any notes for upgrading from 4.0 to 4.0.1?

    The installer looks like it just overwrites the existing configuration.

  2. Currently we are using Atlassian Bamboo version 2.2.2 & we are in a plan to upgrade it.

    could you please suggest that to which next version we can go ahead to upgrade it or there is also a way to upgrade it to the latest version of Bamboo i.e. 5.3.

  3. Hi Sagar,

    If you have a look at the Bamboo Upgrade Guide it spells out the steps you will need to take to upgrade your version of Bamboo.

    It looks as if you will need to follow:

    2.2.2 > 2.6.3 > 2.7.4 > 5.3

    I hope this helps.

  4. Anonymous

    Thanks Nathan for info & we will proceed accordingly.

  5. Anonymous

    Hi Team, 

    Currently I am facing 1 issue with Bamboo remote agent & it went offline with below error.


    2014-01-28 04:10:31,324 FATAL [QuartzScheduler_Worker-2] [AgentHeartBeatJob] Full stack trace
    org.springframework.remoting.RemoteAccessException: Cannot access JMS invoker remote service at [null]; nested exception is javax.jms.JMSException: No space left on device
    Caused by:
    javax.jms.JMSException: No space left on device
    at org.apache.activemq.util.JMSExceptionSupport.create(
    at org.apache.activemq.ActiveMQConnection.syncSendPacket(
    at org.apache.activemq.ActiveMQSession.send(
    at org.apache.activemq.ActiveMQMessageProducer.send(
    at org.jencks.amqpool.PooledProducer.send(
    at org.logicblaze.lingo.jms.impl.OneWayRequestor.doSend(
    at org.logicblaze.lingo.jms.impl.MultiplexingRequestor.doSend(
    at org.logicblaze.lingo.jms.impl.OneWayRequestor.send(
    at org.logicblaze.lingo.jms.impl.OneWayRequestor.send(
    at org.logicblaze.lingo.jms.impl.MultiplexingRequestor.request(
    at com.atlassian.bamboo.lingo.BambooMultiplexingRequestor.request(
    at org.logicblaze.lingo.jms.JmsClientInterceptor.invoke(
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(
    at $Proxy1.updateRemoteAgentStatus(Unknown Source)
    at com.atlassian.bamboo.quartz.SystemAuthorizedThreadPool$
    at org.quartz.simpl.SimpleThreadPool$
    Caused by: org.apache.activemq.kaha.RuntimeStoreException: No space left on device
    at org.apache.activemq.kaha.impl.container.MapContainerImpl.write(
    at org.apache.activemq.kaha.impl.container.MapContainerImpl.put(
    at org.apache.activemq.command.ActiveMQMessage.visit(
    at org.apache.activemq.transport.TransportFilter.onCommand(
    at org.apache.activemq.transport.WireFormatNegotiator.onCommand(
    at org.apache.activemq.transport.InactivityMonitor.onCommand(
    at org.apache.activemq.transport.TransportSupport.doConsume(
    Caused by: No space left on device
    at Method)
    at org.apache.activemq.kaha.impl.container.MapContainerImpl.write(
    ... 22 more
    2014-01-28 04:10:31,486 FATAL [QuartzScheduler_Worker-2] [AgentHeartBeatJob] Invalid heartbeat. Exiting.


    Could you please suggest on this to me to resolve out the issue.

    Thanks & regards, 

    Sagar Lohkare

    1. Hi Sagar,

      This looke well beyond my ability to help with in a comment - can you please raise a ticket with support, and ask them to look at it?


      Nathan Pye