This page describes the supported platforms for Bamboo 5.x.x.

Key: (tick) = Supported; (error) = Not Supported

Java

 

 

Oracle JDK

(tick) 1.7

(tick) 1.6

(error) 1.51

For the server, it is not enough to have just the JRE. Please ensure that you have the full JDK.

You can download the Java SE Development Kit (JDK) from the Oracle website.

Once the JDK is installed, you will need to set the JAVA_HOME environment variable, pointing to the root directory of the JDK. Some JDK installers set this automatically (check by typing 'echo %JAVA_HOME%' in a DOS prompt, or 'echo $JAVA_HOME' in a shell). You need to do this before installing Bamboo, as Bamboo will automatically configure JDK capabilities based on the system environment variables on your machine.

1Note that your agents can build software with any JDK version. You only need to run the agent and server using a supported JDK.

Note: Bamboo does NOT work with OpenJDK 1.6.0

OpenJDK

(tick) 1.7

Operating Systems

 

 

Microsoft Windows

(tick)

Bamboo is a pure Java application and should run on any platform, provided all the JDK requirements are satisfied.

If you are using Linux/UNIX: A dedicated user should be created to run Bamboo, as Bamboo runs as the user it is invoked under and therefore can potentially be abused. Here is an example of how to create a dedicated user to run Bamboo in Linux:
$ sudo /usr/sbin/useradd --create-home --home-dir /usr/local/bamboo --shell /bin/bash bamboo

Linux / Solaris

(tick)

Apple Mac OS X

(tick)

Application Servers

 

 

Apache Tomcat

(tick) 7.0.x

(tick) 6.0.x

(tick) 5.5.x

Deploying multiple Atlassian applications in a single Tomcat container is not supported. We do not test this configuration and upgrading any of the applications (even for point releases) is likely to break it. There are also a number of known issues with this configuration (see this FAQ for more information).

We also do not support deploying multiple Atlassian applications to a single Tomcat container for a number of practical reasons. Firstly, you must shut down Tomcat to upgrade any application and secondly, if one application crashes, the other applications running in that Tomcat container will be inaccessible.

Finally, we recommend not deploying any other applications to the same Tomcat container that runs Bamboo, especially if these other applications have large memory requirements or require additional libraries in Tomcat's lib subdirectory.

Databases

 

 

MySQL

(tick) 5.x with JDBC Connector/J 5.1

(error) 5.0.x

 

PostgreSQL

(tick) 8.x + with PostgreSQL Driver 8.4.x

(tick) 9.x + with PostgreSQL Driver 9.3.x

 

Microsoft SQL Server

(tick) 2008 with JTDS 1.2.2

(tick) 2005 with JTDS 1.2.2

 

Oracle

(tick) 11G with Oracle 11.2.x

(error) 10G

 

HSQLDB

(tick) (for evaluation only)

Bamboo ships with a built-in HSQL database, which is fine for evaluation purposes but is somewhat susceptible to data loss during system crashes. For production environments we recommend that you configure Bamboo to use an external database.

Web Browsers

 

 

Microsoft Internet Explorer

(tick) 11

(tick) 10

(tick) 9

(error) 8

 

Mozilla Firefox

(tick) Latest stable version supported

 

Safari

(tick) Latest stable version supported

 

Chrome

(tick) Latest stable version supported

 
Source Repositories

 

 

Mercurial

(tick) client: 1.6-2.1.x

(error) client: 2.1.0

NOTE : Mercurial 2.1 has a bug that makes it incompatible with Bamboo. Please use Mercurial 2.1.1 or later.

Subversion

(tick) with server 1.5-1.7

  • Bamboo 4.2, and later versions, support Subversion 1.7, but use the Subversion 1.6 Workspace Format by default to keep backwards compatibility with older Subversion working copies. You can set the bamboo.svn.wc.format system property if your Bamboo plans need to use Subversion 1.7 commands as part of your build scripts. See Setting Bamboo to Support Subversion 1.7 Workspace Format for details.
  • Bamboo works with Subversion 1.8, but does not yet support the 1.8 Workspace Format.

Git

(tick) with client 1.7+

 

Perforce

(tick)

 

CVS

(tick) 

 

Notes

Please note, Atlassian does not support custom elastic images. Consider customising the elastic agents started from your existing image instead. See Creating a custom elastic image.

  • No labels

7 Comments

  1. Anonymous

    Aug 22, 2011

    What is the installed size of Bamboo? we're doing planing to setup the JIRA server and need to be able to add up the storage space.

    thanks--

    1. AntonA

      Aug 23, 2011

      The raw installed size is about 140MB.

      I am not sure if you are actually asking about how much disk space Bamboo will use once it's running.

      That heavily depends on your usage pattern, i.e. how many plans you will have, how many tests each plan will be executing (i.e. how large your test results are going to be), how many artifacts you are going to have and how large they are.

      We have Bamboo instances that get away with using 100MB on top of the installed size and ones that go up to 1TB.

      The best thing to do is allocate about 200-300MB on top of the installed size, start small and see how much you will need on top if your usage will grow.

      Cheers,
      Anton

  2. Gael CROVA

    Feb 15, 2013

    Hi,

    Do you have same page regarding supported platforms and operating systems for Bamboo Agents ?

    I'm specially interested to know if bamboo agent can run on z OS (or if a "running" JDK is enough).

    Thanks in advance

    Regards

    Gael

  3. Anonymous

    Jun 06, 2013

    I've added JAVA_HOME environment variable but the installation fails saying it can't locate java. This is on Windows 2008 with JDK 1.7.

    Is there any further information on getting this to work? 

  4. Anonymous

    Jun 07, 2013

    I am also having the same issue of JAVA_Home. It is saying it can't locate Java. On Windows 7 JRE 7 installed

  5. Jason McIntee

    Jun 13, 2013

    Did you make sure there are no spaces in your java_home path location. Atlassian doesn't really work well when that is the case.

  6. TIm S

    Dec 28, 2014

    For those of you having issues with bamboo not finding the jre install, even though JAVA_Home is defined:

    I'm just about through my run of the dragon challenge, and came across this issue, I believe that bamboo needs to match the jdk you installed so far as 32bit vs 64bit goes. The dragon challenge guide suggests installing the 32bit jdk, which I did. I installed the x64 version of all of the other tools however, and attempted to do the same with Bamboo, receiving this error. Switching to the 32bit version of bamboo has resolved this error for me and enabled me to continue through the install process.