Bamboo, Atlassian’s continuous integration and delivery server, is a very popular application amongst development teams. Historically, there have been two versions of Bamboo: Bamboo Cloud and Bamboo Server. However, after January 31, 2017, there will only be one option, Bamboo Server. As Atlassian announced back in May, Bamboo Cloud is being discontinued.
If you’ve been using Bamboo Cloud, now’s the time to get Bamboo Server up and running in your environment! Here’s what you need to know…
Bamboo Server Licensing
Bamboo Server licensing is really quite straightforward. There are “free trial” licenses and there are paid licenses. The free licenses are good for 30 days if you get the trial key and download the installers at the Atlassian website, and up to six months if you get the trial key from an authorized Atlassian Reseller such as Coyote Creek. The paid licenses are perpetual licenses, with the cost based on the number of agents. Paid licenses come with 12 months of software maintenance, including all updates and online support.
Bamboo Cloud to Bamboo Server Migration Tips
Atlassian provides details of the migration path on their website. However, like all migrations, things don’t always go as smoothly as the instructions imply they will.
Based on our experience in the field, here are some things to watch for when migrating from Bamboo Cloud to Bamboo Server:
- Agent Setup Issues – If you’re using agents in Bamboo Cloud, all of the configuration is done for you. You don’t have to deal with configuring different compilers for different types of builds, setting up your agent servers, etc. On Bamboo Server you need to do all of this yourself. You need to evaluate the agent setup that you have in Bamboo Cloud and then replicate that infrastructure as closely as possible on Bamboo Server. Getting the databases configured and the servers set up takes a certain amount of infrastructure knowledge. If you don’t have it, enlist the help of someone who does.
- Git Version Inconsistencies – Take a close look at the version of the Git version control system that you have on the local server on which you’re setting up Bamboo. This version must be the same as or newer than the Git you were using in the cloud. If not, Bamboo Server won’t work. There’ll be nothing to compile if your version control system isn’t working.
- Data Export Problems – If you need to export attachments that are over 24 GB, you won’t be able to do this directly through the cloud. Instead, you’ll have to ask Atlassian to export the attachments, wrap it up and send it to you for import into your new system. You might need to do this for your database dump file as well. Theoretically you can export your database dump file as a zip file, but I’ve seen several instances where if you try to do this through the user interface it simply doesn’t work.
- Performance Issues – Configuring the Bamboo application to use the proper resources from Java and provide peak performance requires some Tomcat expertise. If you don’t have the server administration know-how to do this, your Bamboo Server might not perform as well as possible.
- Broken Application Links – Once you have Bamboo Server up and running you must reapply the links to whatever applications you’re using that link to Bamboo (such as JIRA), to ensure they point to the new server location.
Need help migrating from Bamboo Cloud to Bamboo Server, or getting proper Bamboo Server licensing in place? Give us a call. As Atlassian Platinum Experts, we’re here for you.
