This is the documentation for Bamboo 5.8. View this page for the

Unknown macro: {spacejump}

of Bamboo, or visit the latest Bamboo documentation.

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

See also Bamboo best practice - system requirements.

Key(tick) = Supported; (warning) = Deprecated; (error) = Not Supported

Java

 

 

Oracle JDK

(tick) 1.8

(warning) 1.7

(warning) 1.6

(error) 1.5

For the Bamboo 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 command 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.

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

(warning) Support for Oracle Java 1.6 and 1.7 is deprecated. See End of support announcements for Bamboo.

(error) Bamboo does NOT support OpenJDK 1.6.

OpenJDK

(tick) 1.8

(warning) 1.7

(error) 1.6

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

(tick)

Solaris(tick) with Java JDK 1.7.x

Apple Mac OS X

(tick)

Application Servers

 

 

Apache Tomcat

(tick) 7.0.x

We only support the Tomcat version bundled with Bamboo.
Databases

 

 

MySQL

(tick) 5.5, 5.6

(warning) 5.1

(error) 5.0.x

MySQL is supported when used with the JDBC Connector/J 5.1.

(warning) Support for MySQL 5.1 is deprecated. See End of support announcements for Bamboo.

 

PostgreSQL

(tick) 9.0, 9.1, 9.2, 9.3, 9.4

(warning) 8.x

PostgreSQL is supported when used with the PostgreSQL Driver 9.3.x.

(warning) Support for PostgreSQL 8 is deprecated. See End of support announcements for Bamboo.

 

Microsoft SQL Server

(tick) 2012

(warning) 2008 with JTDS 1.2.2

(warning) 2005 with JTDS 1.2.2

(warning) Support for Microsoft SQL Server 2005 and 2008 is deprecated. See End of support announcements for Bamboo.

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.8

  • 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, and supports the 1.8 Workspace Format.

Git

(tick) with client 1.7.9+

 

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