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.

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.

Bamboo 2.0 Beta 3 introduces a number of new features, including Perforce support and the ability to connect to Oracle and MS SQL as external databases. A number of significant fixes have been included as well, improving the overall quality and experience of the beta.

What's New in Bamboo 2.0 Beta 3?

Perforce Support — Bamboo brings back out of the box support for Perforce source repositories. A number of changes have been made to Perforce configuration to ensure that it works correctly with distributed builds. Read more about configuring Perforce.

Oracle and MS SQL Server Support — By popular request, Bamboo's supported databases now include Oracle and MS SQL Server. Read more about connecting Bamboo to Oracle and MS SQL Server.

Major Bug Fixes — Bamboo now works with PostgreSQL and MySQL correctly. Please see the relevant Postgresql and MySQL JIRA issues for details about the fixes.

Major Bug Fixes

• Previously, Bamboo determined which agents could build a plan when the plan was queued, but would then incorrectly ignore any subsequent changes (including disabling the agent). Bamboo will now correctly update where plans can be built, even if changes are made after the plan has been queued.

For the Developers

• The new 'RepositoryEventAware' interface allows you to implement custom actions before and/or after retrieving source code from your repository. Read more about extending the standard repository functionality.

JDK and Builders page now included in Bamboo 2.0 Beta

• The JDK and Builder pages which were temporarily removed from Bamboo for the 2.0 Beta have now been restored.

Secured Remote Agents are now Supported

• Remote agents can now be secured with the appropriate SSL configuration. Read more about Securing your Remote Agents.
  We strongly recommend that you do not enable remote agent installation on any Bamboo instance accessible from a public or untrusted network without securing your remote agents. If you choose to enable your remote agents without securing them, please read this security advisory to understand the security implications.

Changes to Client Workspace Configuration for Perforce

• If you use Perforce, you can now choose whether your want Bamboo to manage your client workspace (i.e. set the client root) or manage it yourself. Read more about Perforce configuration.

'Shared Local Capabilities' are now called 'Local Server Capabilities'

• All references to 'Shared Local Capabilities' (or equivalent terminology) have been changed to 'Local Server Capabilities' in the Bamboo user interface.

Quiet Period Functionality Supported for Subversion & Perforce

By popular request, Quiet Period parameters can now be specified for Subversion and Perforce when configuring a source repository for a build plan. You can choose to set how long Bamboo should wait after a commit before triggering a build, and the number of times it retries before initiating a build. Read more about configuring Subversion and Perforce source repositories.

'Force Clean Builds' Supported

Also by popular request, you can now force Bamboo to run 'Clean Builds' in a build plan. That is, the source directory is removed and then checked out from the repository prior to each build. Read more about this function in Specifying a Plan's Source Repository.

Edit and Rename Capabilities

You can now edit capabilities in Bamboo, as listed below:

• If you are editing a Builder capability, you can modify the 'Path' of the builder.
• If you are editing a JDK capability, you can modify the 'Java Home' of the JDK.
• If you are editing a Custom capability, you can modify the 'Value' of the capability.
• If you are editing a Perforce capability, you can modify the 'Perforce Executable' path.
  

You can also rename a capability. This is reflected in any plans that the capability is specified as a requirement for.

Read more about editing capabilities and renaming capabilities.

View Agents and Plans related to a Capability

A 'View Capability' screen is now available in Bamboo 2.0. This screen lists the agents that have/inherit a particular capability, as well as which plans have the capability specified as a requirement.

Read more about viewing capabilities.