Upgrading Bamboo with Crowd to Bamboo 3.2

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

The instructions on this page are for customers who are currently using Bamboo with Crowd, and want to upgrade to Bamboo 3.2. These instructions complement the instructions on the Bamboo 3.2 Upgrade Guide.

In this upgrade process, you may need to upgrade your Crowd installation in addition to upgrading Bamboo.

On this page:

Upgrade Crowd to Crowd 2.3.1

Bamboo 3.2 ships with Crowd 2.3 integration libraries. Before upgrading Bamboo to Bamboo 3.2, you must upgrade your Crowd instance to at least Crowd 2.3.1. This will result in better performance, particularly if you have a large user base. For instructions on how to upgrade Crowd, see the Crowd Upgrade Guide

Testing the Crowd Upgrade

If you would like to test whether Crowd 2.3.1 will work properly with your existing Bamboo installation, do the following:

  1. Replace your crowd-integration-clientwith version 2.3.1, i.e.

    rm Bamboo-3.1.4/webapp/WEB-INF/lib/crowd-integration-client*.jar
    cp atlassian-crowd-2.3.1/client/crowd-integration-client-2.3.1.jar Bamboo-3.1.4/webapp/WEB-INF/lib
    rm Bamboo-3.1.4/webapp/WEB-INF/classes/crowd-encache.xml
    cp atlassian-crowd-2.3.1/client/conf/crowd-encache.xml Bamboo-3.1.4/webapp/WEB-INF/classes
    
  2. Copy atlassian-user-crowd-provider-3.2.jar from the Bamboo 3.2 distribution into your old Bamboo WEB-INF/libdirectory to avoid "NoClassDef" exceptions due to missing CrowdUserManager class, i.e.

    cp Bamboo-3.2/webapp/WEB-INF/lib/atlassian-user-crowd-provider-3.2.jar Bamboo-3.1.4/webapp/WEB-INF/lib
    

Upgrade Bamboo to Bamboo 3.2

After upgrading Crowd, you can upgrade Bamboo to Bamboo 3.2 using one of the following methods:

(Recommended) Method 1. Perform an "inline" upgrade without exporting/importing.

This method is similar to a regular Bamboo upgrade. You will install Bamboo 3.2, copy the Crowd settings over from your old Bamboo instance and point your new instance at your old Bamboo home.

  1. Download Bamboo 3.2 from the Bamboo download centre and install it. Do not start it.
  2. Copy the Crowd settings from your old Bamboo instance to the new Bamboo 3.2 instance, i.e.
    • rm Bamboo-3.2/webapp/WEB-INF/classes/atlassian-user.xml
    • cp Bamboo-3.1.4/webapp/WEB-INF/classes/atlassian-user.xml Bamboo-3.2/webapp/WEB-INF/classes
    • rm Bamboo-3.2/webapp/WEB-INF/classes/crowd.properties
    • cp Bamboo-3.1.4/webapp/WEB-INF/classes/crowd.properties Bamboo-3.2/webapp/WEB-INF/classes
  3. Configure your new Bamboo instance to use the old bamboo-home (in webapp/WEB-INF/classes/bamboo-init.properties).
  4. Start up Bamboo.
    (info) You can remove crowd.properties, atlassian-user.xml and crowd-encache.xml files from Bamboo-3.2/webapp/WEB-INF/classes folder after this, if you wish (as per BAM-9318).

Method 2. Import through the administration panel.

This method requires you to install Bamboo 3.2 (including running the setup wizard), update your atlassian-user.xml and crowd.properties files in Bamboo, then import the data from your old Bamboo instance.

  1. Back up your existing Bamboo installation. See Bamboo upgrade guide for instructions.
  2. Download and install your new Bamboo 3.2 instance, including completing the setup wizard.
  3. Connect your new Bamboo 3.2 instance to your Crowd instance by editing Bamboo-3.2-home/xml-data-configuration/atlassian-user.xml.
    (warning) Please note this is not the same file as Bamboo-3.2/webapp/WEB-INF/classes/atlassian-user.xml
    Your file should look like this after editing:

    <atlassian-user>
        <repositories>
            <crowd name='Crowd Repository' key='crowd'/>
        </repositories>
    </atlassian-user>
    
  4. Edit Bamboo-3.2-home/xml-data-configuration/crowd.properties and update the credentials and URLs.
    (warning) Please note this is not the same file as Bamboo-3.2/webapp/WEB-INF/classes/crowd.properties
  5. Restart Bamboo.
  6. Do the import from the administration panel, as described in Importing data from backup.
    (info) You can remove crowd.properties, atlassian-user.xml and crowd-encache.xml files from Bamboo-3.2/webapp/WEB-INF/classes folder after this, if you wish (as per BAM-9318).

Method 3. Upgrade Bamboo and import via the setup wizard

This method is similar to option 2. You are required to install Bamboo 3.2, however data is imported from your old Bamboo instance during the setup wizard. The atlassian-user.xml and crowd.properties files are updated in Bamboo, after the import.

Please be aware, that Bamboo will return error messages stating that the import has failed in this method. However, this is expected behavior and the resultant upgrade will still work correctly.

  1. Back up your existing Bamboo installation. See Bamboo upgrade guide for instructions.
  2. Download and install your new Bamboo 3.2 instance.
  3. Run the setup wizard. When you are prompted to import data, import data from your old Bamboo installation. At the end of the import, Bamboo will state that there is no user with administration privileges and will ask you to contact Atlassian support. However, your plans and builds will be properly migrated with the exception that the user management is not working yet i.e. you won't be able to log in to Bamboo.
  4. Shut down the Bamboo instance.
  5. Connect your new Bamboo 3.2 instance to your Crowd instance by editing Bamboo-3.2-home/xml-data-configuration/atlassian-user.xml.
    (warning) Please note this is not the same file as Bamboo-3.2/webapp/WEB-INF/classes/atlassian-user.xml
    Your file should look like this after editing:

    <atlassian-user>
        <repositories>
            <crowd name='Crowd Repository' key='crowd'/>
        </repositories>
    </atlassian-user>
    
  6. Edit Bamboo-3.2-home/xml-data/configuration/crowd.properties and update the credentials and URLs.
    (warning) Please note this is not the same file as Bamboo-3.2/webapp/WEB-INF/classes/crowd.properties
  7. Start Bamboo
    (info) You can remove crowd.properties, atlassian-user.xml and crowd-encache.xml files from Bamboo-3.2/webapp/WEB-INF/classes folder after this, if you wish (as per BAM-9318).

Congratulations! You should now be able to log into your upgraded Bamboo instance and have your users managed by Crowd.

Last modified on May 26, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.