You can clone an existing Bamboo instance by getting a new Bamboo instance in the same version and using the setup of the existing one.

For example, you may want to transfer a snapshot of your current production Bamboo instance to a test server.

Cloning Bamboo can be a step in preparation for migrating to another database or for upgrading.

If you are using JIRA or Crowd for user management, the URL of the Bamboo server may change when you clone the Bamboo instance, in which case you will need to edit that setting for the Bamboo application in JIRA/CROWD to match the new URL.

License

Development licenses are available for any Commercial or Academic license. Create one or contact us for help.



On this page:

Cloning a Bamboo instance to a new server

To clone a Bamboo instance to a new server:

  1. Export/Backup your original Bamboo instance.

  2. Install the same version of Bamboo on the new server.

    If you are cloning a Bamboo instance on the same server, make sure that the original Bamboo instance doesn't have the same <bamboo-install> installation path as the new Bamboo instance.

  3. On the new server, in the new <bamboo-install> directory, go to webapp/WEB-INF/classes/ and open the bamboo-init.properties file.In the bamboo-init.properties file, set the new <bamboo-home> path.

    If you are cloning a Bamboo instance on the same server, make sure that the new Bamboo instance doesn't have the same <bamboo-home> path as the original Bamboo instance.

  4. Start the new Bamboo instance and import the existing export/backup data prepared in Step 1.





The installation path is referred to as <bamboo-install> and points to the directory into which you extracted the Bamboo package during the installation. It is different from the <bamboo-home> path which points to the directory where Bamboo data is stored.







Alternative cloning scenario

If your current instance has grown too large and export/import does not work, you can still clone your instance by using an alternative backup and restore strategy.
The approach is to clone the <bamboo-home> content and make it available to the new Bamboo instance:

  1. Stop the original Bamboo instance.

  2. Create a backup:

    embedded DB

    external DB

    Compress the original <bamboo-home> directory into a .zip file. The embedded database is included in the directory.


    • Compress the original <bamboo-home> directory into a .zip file.
    • Create a database backup with the native tools.

    You can reduce the size of a compressed <bamboo-production-home>file by deleting the xml-data/build-dir directory that contains working copies of the checked-out sources.

    For more information about migrating databases, see Moving your Bamboo data to a different database.

  3. Restart the original Bamboo instance.

  4. Install the same version of Bamboo on the new server.

    If you are cloning a Bamboo instance on the same server, make sure that the new Bamboo instance doesn't have the same <bamboo-install> installation path as the original Bamboo instance.
  5. Transfer the compressed original <bamboo-home> directory to the new server where you installed the new Bamboo instance.
  6.  Replace the content of the new <bamboo-home> directory with the unzipped <home-directory> content.

  7. On the new server, in the new <bamboo-install> directory, go to webapp/WEB-INF/classes/ and open the bamboo-init.properties file.In the bamboo-init.properties file, set the new <bamboo-home> path.

    If you are cloning a Bamboo instance on the same server, make sure that the new Bamboo instance doesn't have the same <bamboo-home> path as the original Bamboo instance.

  8. (External DB only) Create a new database for the cloned instance and import the external database backup.

  9. In the new <bamboo-home> directory, open:

    • bamboo.cfg.xml
    • xml-data/configuration/administration.xml

    and change the server names/IP addresses according to the new location.

  10. (External DB only) Go to the new <bamboo-home> directory, open the bamboo.cfg.xml file, and enter the new database connection details and credentials.

  11. Start the new Bamboo instance.

Next steps

  • (Optional) You can upgrade the new Bamboo instance.
  • If the new server has different locations for:
    • JDKs
    • Ant
    • Maven
    • Perforce
    • Msbuild tools
    adjust the settings in the server capabilities settings to match the locations on the new server.
  • No labels