Bamboo 2.0 : Bamboo 2.0 Beta Upgrade Guide
This page last changed on Apr 02, 2008 by alui.
This page contains a live aggregate of all version-specific upgrade guides for the Bamboo 2.0 Beta. How to read the Bamboo 2.0 Beta Upgrade Guides
Bamboo 2.0 Beta Upgrade Guides
Upgrading to Bamboo 2.0 Beta 1
Upgrading from Bamboo 1.1.xYou will need to:
Upgrading from Bamboo 1.0.xYou will need to:
1. Adding a Broker URL property.Bamboo uses a messaging broker to communicate with it's remote build agents. To ensure this works properly, a URL must be specified. This URL is where Bamboo will set up its embedded broker. Remote agents will also be provided with this URL on startup. To specify the broker URL, please add a bamboo.jms.broker.url property in your bamboo.cfg.xml file, located inside the Bamboo home directory. For example: <property name="bamboo.jms.broker.uri">tcp://HOSTNAME:54663</property> where HOSTNAME is the canonical name of your Bamboo server. Please note, as remote agents use this URL to communicate to the server, you should take care not to specify localhost as the host name in the broker URL. If no broker URL is found in bamboo.cfg.xml, Bamboo will default the broker URL to tcp://HOSTNAME:54663 in the bamboo.cfg.xml file, as seen in the example above. Bamboo will also append the parameter wireFormat.maxInactivityDuration=0 by default to any broker URL coming from bamboo.cfg.xml. 2. Changes to Server ConfigurationJDK supportBamboo 2.0 requires JDK 1.5 (i.e. JDK 1.4 is no longer supported). Please note that this does not affect the actual builds: it is only the Bamboo server itself that must be running JDK 1.5. Database changesThe release of 2.0 will include some changes to column names in the database as follows:
These fields have also had types changed to CLOB to increase their maximum lengths. PluginsIf you are using external or custom plugins, please make sure that your plugins compile against Bamboo 2.0 before upgrading.
3. Changes to Build Queues and Build PlansBamboo 2.0 introduces the concepts of agents and capabilities. To preserve the functionality of your existing plans, JDKs, Builders and Build Queues, the following will automatically happen during the upgrade: Conversion of Build Queues to AgentsPrior to Bamboo 2.0, you could have multiple build queues. In Bamboo 2.0, there is now only one build queue, but multiple agents (see diagram). As part of the upgrade process,
If you wish to change this after the upgrade, please see 02. Configuring Agents and Capabilities and 1.2.4 Specifying a Plan's Capability Requirements. Conversion of Builders to CapabilitiesPrior to Bamboo 2.0, your builders (e.g. Maven) were defined globally. In Bamboo 2.0, builders are now defined as agent capabilities and specified as plan requirements. As part of the upgrade process,
If you wish to change this after the upgrade, please see 2.8 Configuring Capabilities and 1.2.4 Specifying a Plan's Capability Requirements. Conversion of JDKs to CapabilitiesPrior to Bamboo 2.0, your JDKs (e.g. JDK 1.5) were defined globally. In Bamboo 2.0, JDKs are now defined as agent capabilities and specified as plan requirements. As part of the upgrade process,
If you wish to change this after the upgrade, please see 2.8 Configuring Capabilities and 1.2.4 Specifying a Plan's Capability Requirements. Upgrading to Bamboo 2.0 Beta 2![]() No additional upgrade tasks are required to upgrade from Bamboo 2.0 Beta 1 to 2.0 Beta 2. Upgrading to Bamboo 2.0 Beta 3
1. Changes to RepositoriesBamboo 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 CapabilityWith 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,
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 2.8.4 Configuring a new Perforce Capability for further details on creating Perforce capabilities. Upgrading to Bamboo 2.0 Beta 4![]() No additional upgrade tasks are required to upgrade from Bamboo 2.0 Beta 3 to 2.0 Beta 4. Upgrading to Bamboo 2.0 Beta 5![]() No additional upgrade tasks are required to upgrade from Bamboo 2.0 Beta 4 to 2.0 Beta 5. Upgrading to Bamboo 2.0 Beta 6![]() 1. Changes to Perforce Workspace ManagementIf you use Perforce, you can now choose whether you want Bamboo to manage your workspace or whether you want to manage it yourself. Prior to this release, Bamboo would automatically manage your workspace (i.e. changed the client root). Hence, if you want to manage your workspace in this release, you will need to reset your client roots. Upgrading to Bamboo 2.0 Beta 8![]() No additional upgrade tasks are required to upgrade from Bamboo 2.0 Beta 6 to 2.0 Beta 8. Upgrading to Bamboo 2.0 Beta 9![]() No additional upgrade tasks are required to upgrade from Bamboo 2.0 Beta 8 to 2.0 Beta 9. |
![]() |
Document generated by Confluence on Apr 14, 2008 01:39 |