Documentation for Bamboo 4.1.x. Documentation for earlier versions of Bamboo is available too.

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

8 February, 2008

Atlassian Software Systems presents Bamboo 2.0 Beta

 Bamboo 2.0 will be launched in early 2008 and will introduce a number of new features, including the ability to run distributed builds, flexible build agent management and memory usage improvements.

Because Bamboo 2.0 will introduce major architectural changes, the Bamboo 2.0 Beta program is being provided to enable you to preview the upcoming features and perform preliminary testing.

Please note that this release is a beta and should not be used on production systems.

Upgrading to Bamboo 2.0 Beta

Bamboo 2.0 Beta can be downloaded from the Bamboo Download Centre. Before upgrading, please refer to the Bamboo 2.0 Beta Upgrade Guide. You must upgrade to Bamboo 1.2.x before upgrading to 2.0.

What's New in Bamboo 2.0?

 Distributed Builds — This release introduces the ability to run distributed builds. You will find this particularly useful if you need to run your builds in different geographic locations, or on different platforms. Simply install the new Bamboo Agent on your additional build servers, and your main Bamboo 2.0 server will be able to manage them. We have also provided a number of plugin points in case you need to control your distributed builds programmatically.

 Flexible Build Agent Management — Bamboo 2.0 also gives you much more flexibility in managing your builds. Build queues are no longer required, with the introduction of requirements and capabilities. You can direct builds to be run on a particular agent, by specifying build plan requirements to match the builder, JDK and custom capabilities that you have set up for the agent. Read more about agents and capabilities here.

 Memory Usage Improvements — The underlying engine for Bamboo has been revamped to decrease memory usage. You will notice a distinct improvement in the performance of your builds, especially if you have very large logs.

Security Considerations

(warning) Important security information for the Bamboo 2.0 Beta has been published. Please refer to the security advisory for details.

Known Issues

The following issues are applicable at the time of the Bamboo 2.0 Beta 1 release. Please refer to the aggregated Bamboo 2.0 Beta Release Notes to review the complete list of issues and fixes for each beta release.

  • Perforce is not supported in the Bamboo 2.0 Beta (but will be supported in the official Bamboo 2.0 release).
  • Bamboo currently does not work with MySQL. See BAM-2260 for further details.
  • Plans currently cannot be edited, if Bamboo is integrated with a PostgreSQL database. See BAM-2208 for further details.
  • Secured remote agents are not supported in the Bamboo 2.0 Beta (but will be supported in the official Bamboo 2.0 release). Please see the Bamboo security advisory for further details.
  • JDK and Builders pages have not been included in the Bamboo 2.0 Beta (but will be supported in the official Bamboo 2.0 release).
  • Please note that builds are currently allocated to agents during queuing time, not execution time. This may occasionally mean that a build is executed by an agent that you have disabled, which is slightly different from the functionality described in Monitoring agent status. For example:
    1. Agent A is enabled and is currently executing a build for Plan X.
    2. Plan Y submits a build to the queue, and the queue assigns the build to Agent A.
    3. You disable Agent A.
    4. Agent A completes Plan X's build.
    5. Although agent A is disabled, it will still run Plan Y's build, because it was determined as executable when plan Y was queued.

Updates and Fixes in this Release

Please help us with the final 2.0 release by reporting any bugs and issues you find, in the Bamboo project at jira.atlassian.com.

key summary priority status

Data cannot be retrieved due to an unexpected error.

View these issues in Jira