Bamboo 2.0 Beta 3 Upgrade Guide

Upgrading to Bamboo 2.0 Beta 3

These instructions outline how to upgrade Bamboo from version 2.0 Beta 2 to 2.0 Beta 3. If you are upgrading from a version prior to 2.0 Beta 2, please refer to the aggregated upgrade guides for details on the previous beta releases.

It is strongly recommended that you back up your xml-data directory before proceeding. You are also strongly recommended to back up your database due to schema changes in this release. For full instructions please follow the Bamboo Generic Upgrade Guide. Additionally, please note the following:

1. Changes to Repositories

Bamboo 2.0 introduces the concepts of agents and capabilities. To preserve the functionality of your existing Repositories, the following will automatically happen during the upgrade:

Conversion of Perforce P4 Client Application Location to a Capability

With the introduction of remote agents in Bamboo 2.0, the location of the Perforce P4 client application now needs to be specified as a capability. To create build plans using Perforce as repository, a shared local capability must be created for the P4 client application location. In addition, agent-specific remote capabilities must be created for each remote agent using Perforce.

As part of the upgrade process,

• A shared local Perforce capability will be created for the Perforce P4 client application location. The upgrade task reads this information from the system's environment variables. If the Perforce P4 client application location has not been specified as an environment variable, the shared local capability will need to be set up manually.

The upgrade task will not create agent-specific Perforce capabilities for any remote agents. These capabilities will need to be set up manually.

Please see Configuring a new Perforce Capability for further details on creating Perforce capabilities.