This documentation relates to Bamboo 3.4.x
If you are using an earlier version, please view the previous versions of the Bamboo documentation and select the relevant version.
Skip to end of metadata
Comment: Corrected links that should have been relative instead of absolute.
Go to start of metadata

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

19 February 2008
Atlassian is proud to announce the release of Bamboo 2.0 Beta 2.

This point release includes more than 10 minor fixes and improvements. Bamboo 2.0 Beta 2 can be downloaded here.

Before upgrading, please read the Bamboo 2.0 Beta 2 Upgrade Guide. If you are upgrading from a version of Bamboo prior to the Bamboo 2.0 Beta, please read all of the Bamboo 2.0 Beta Release Notes and Bamboo 2.0 Beta Upgrade Guides before upgrading.

Known Issues

The following issues are applicable at the time of the Bamboo 2.0 Beta 2 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 issues fixed

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.