Index
Downloads (PDF, HTML & XML formats)
[Bamboo Knowledge Base Home]
Documentation for Bamboo 4.1.x. Documentation for earlier versions of Bamboo is available too. 
This page describes the supported platforms for Bamboo 4.1.x.
Key: 
= Supported; 
= Not Supported
Java Version |
|
|---|---|
| |
| OpenJDK |
|
Operating Systems |
|
Microsoft Windows (2) |
|
Linux / Solaris (2) |
|
Apple Mac OS X (2) |
|
Application Servers |
|
Apache Tomcat (3) |
|
Databases |
|
MySQL |
|
PostgreSQL |
|
Microsoft SQL Server |
|
Oracle |
|
HSQLDB (4) |
|
Web Browsers |
|
Microsoft Internet Explorer |
|
Mozilla Firefox |
|
Safari |
|
Chrome |
|
Source Repositories |
|
Mercurial |
NOTE: Mercurial 2.1 has a bug that makes it incompatible with Bamboo. Please use Mercurial 2.1.1 or later. |
Subversion |
NOTE: Bamboo will work with Subversion 1.7 servers. |
Git |
|
Perforce |
|
CVS |
|
Notes:
1. Oracle JDK:
- 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.
2. Please note:
- 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
3. 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.
4. 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.
5. Note that your agents can build software with any JDK version. You only need to run the agent and server using a supported JDK.
Overview
Content Tools
Apps
Log a request with our support team.
Raise an issue for our developers.
See answers from the community.
Blog and update our documentation.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.
10 Comments
Anonymous
Aug 22, 2011What 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--
AntonA
Aug 23, 2011The 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
Lincoln W. Kliman
Oct 22, 2011Will subversion 1.7 be supported? Should subversion 1.7 be listed with an X for now?
Przemek Bruski
Oct 22, 2011Bamboo should be able to work with 1.7 repository. However, it will not recognise the 1.7 workspace format, so if use any external tools in your build process, make sure they don't upgrade the workspace automatically.
James Dumay
May 30, 2012We have scheduled to upgrade our Subversion support to support Subversion 1.7 working copies for the next release.
You can track our progress here: BAM-10009 - Getting issue details... STATUS
In the meantime, Bamboo will work fine with Subversion 1.7 servers.
Brian Hall
Dec 09, 2011Since your table above lists the only supported version of Mercurial at 1.6, is it possible to use newer versions or are there issues? Specifically, will Bamboo work with Mercurial 1.9.1?
PiotrA
Dec 09, 2011It should be possible to use Bamboo with Mercurial 1.9.1 - you shouldn't encounter problems unless you use some new features from hg (like git subrepositories or similar).
Miro Lehky [Metron]
May 30, 2012Can someone clearify what is meant by....
"
1.7 command line client interoperation"
What is the functional impact of this?
Przemek Bruski
May 30, 2012Bamboo does not understand the new working copy format (WC-NG) introduced in 1.7. If the working copy is upgraded to 1.7, Bamboo will attempt to clear the build working directory, resulting in a full checkout.
James Dumay
May 30, 2012We've scheduled adding support Subversion 1.7 working directories for our next release. You can track it here: BAM-10009 - Getting issue details... STATUS
In the meantime, Bamboo will work fine with Subversion 1.7 servers.