Standalone Bamboo requirements and installation recommendations

Brian Ellis2

We are setting up a standalone Bamboo server for access from multiple offices and would like to get more information on the following:

Which operating system would you recommend installing Bamboo server on?
RHEL, Centos, Ubuntu, SUSE Linux, WIN 2008 R2, Win 2012
We will be building for all OS's so other OS will have to be configured as remote Agents.

Which is the most stable release of the Bamboo server Win or Linux?

Which version is most likely to release new features first, win or Linux?

We are considering hosting our bamboo server in EC2. What are the caveats?

What would be a recommended instance size? m1.large?

Humberto Madeira

>Which operating system would you recommend installing Bamboo server on?

Windows Server Standard 2008 R2 is a good choice.

It will require a 30GB (min) boot disk and about 100GB (min) data disk - (Not sure what 2012 requires, but in general, the more recent the Windows, the more boot space it needs)

In reality, as long as you are using Windows Server, it shouldn't matter that much to Bamboo.

I do recommend that you run it in a VM so that you can snapshot it and take VM backups etc.

>Which is the most stable release of the Bamboo server Win or Linux?

In general, Java and Tomcat work better in Windows than under Linux. Linux, specially the Debian variants (including Ubuntu), have poor support and overly rigid configurations for running Java as a service. The Linux distributions have made good strides lately due to the efforts of the Linux Standard Base, but running on Windows is still more comfy than on Linux.

I wouldn't jump on the Linux bandwagon without a reasonable in-house Linux geek presence, but with it, it should be doable. If you do choose Linux, the boot disk can be as small as 10GB.

>Which version is most likely to release new features first, win or Linux?

Bamboo is a Java application - there is no difference between Windows and Linux versions other than a bit of wrapping that you could implement yourself (we do).

>We are considering hosting our bamboo server in EC2. What are the caveats?

If you run Bamboo on EC2, you will have to expose your bamboo instance to the Internet. If it is meant to be secure, you will need to set up either SSL on Tomcat or set up an SSL reverse proxy on the same host instance (preferably Apache Server 2.4.x - using AJP1.3)

You will also have a bit of an issue with configuring external (usually LDAP) authentication - your authentication service will need to be able to run securely over the internet.

I also have no idea how you would go about securing your Bamboo remote agents to your build servers. Possibly it could be done with support from Atlassian - not sure about it.

Publishing would also have to be addressed - if you hold build artifacts to avoid publishing over the internet, you will probably have to up your data drive size to a terabyte or so.

If you run Bamboo in-house, you can avoid exposing Bamboo to the internet if you want. (your remote offices would have to VPN in however)

Or you can expose it to the internet (so your remote offices don't have to use VPN), but the authentication service doesn't have to pass through the internet, and more importantly, your Bamboo remote agents, and all of the build servers they represent don't have to be secured against the internet.

>What would be a recommended instance size? m1.large?

Depends on your workload, but m1.large is roughly comparable to what we are running in house, plus publishing space, (we run multiple offices) so I would think that would be a reasonable size.