This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

Atlassian maintains public 'default' elastic images, currently they are available for the following operating systems:

  • Amazon Linux
  • Windows (introduced in Bamboo 3.4)

Bamboo's Elastic Bamboo feature uses these images by default. In your list of elastic image configurations, this image will have '(default)' appended to its name.

On this page:

Amazon Linux default image

The Amazon Linux 'default image' uses:

  • the Amazon Linux (a CentOS derivative) operating system.
  • the Bamboo elastic agent.*

and has the following default packages/capabilities:

Default packages/capabilities

Path/value

Builders

 

Ant (version 1.8.2)

/opt/ant-1.8.2

Bash (Command)

/bin/bash

Grails 1.2.2

/opt/grails-1.2.2

Grails 1.3.1

/opt/grails-1.3.1

Maven 1 (version 1.0.2)

/opt/maven-1.0.2

Maven 1.1

/opt/maven-1.1

Maven 2.0 (Maven 2.x) (version 2.0.11)

/opt/maven-2.0.11

Maven 2.1 (Maven 2.x) (version 2.1.0)

/opt/maven-2.1.0

Maven 2.2 (Maven 2.x) (version 2.2.1)

/opt/maven-2.2.1

Maven 3.0 (Maven 3.x) (version 3.0.3)/opt/maven-3.0.3

JDKs

 

JDK 1.5 (version 5u22)

/opt/jdk-5 (for Java Home)

JDK 1.6 (version 6u21)

/opt/jdk-6 (for Java Home)

Others

 

Mercurial 1.4 Executable (version 1.4.1)

/usr/bin/hg

* The agent jar also contains the libraries required to connect to Subversion and CVS.

Windows default image

The Windows 'default image' uses:

  • the Windows 2008 Server R2 64bit operating system, with all updates applied.
  • the Bamboo elastic agent.*

and has the following default packages/capabilities:

Default packages/capabilities

Path/value

Builders

 

Ant (version 1.8.2)

C:\opt\ant-1.8.2

Maven 2.0 (Maven 2.x) (version 2.0.11)

C:\opt\maven-2.0.11

Maven 2.1 (Maven 2.x) (version 2.1.0)

C:\opt\maven-2.1.0

Maven 2.2 (Maven 2.x) (version 2.2.1)

C:\opt\maven-2.2.1

Maven 3.0 (Maven 3.x) (version 3.0.3)C:\opt\maven-3.0.3
NAnt 0.91
C:\opt\nant-0.91

JDKs

 

JDK 1.6 (version 6u29)

C:\Program Files\Java\jdk1.6.0_29

Browsers 
Firefox (FF8)
C:\Program Files (x86)\Mozilla Firefox
Internet Explorer (IE9)
C:\Program Files (x86)\Internet Explorer

Others

 

Git
C:\Program Files (x86)\Git\bin\git.exe

Mercurial 2.0 Executable (version 2.0)

C:\Program Files\TortiseHg\hg.exe

ssh (cygwin) - for hg and git
C:\cygwin\bin\ssh.exe

* The agent jar also contains the libraries required to connect to Subversion and CVS.

Notes

(info) Be aware that the default packages/capabilities listed above may change with each major release of Bamboo. There is a new default image (with its own AMI ID) for each new version of Bamboo. However, older default images will still be available for use.

  • No labels

15 Comments

  1. Anonymous

    Any idea when a Windows/.NET Elastic Bamboo image will be available ?

  2. abd

    Hello

    any update on the Windows/.NET Elastic Bamboo image

    1. Przemek Bruski

      A default image for Windows platform is not available at the moment. You can keep track of this feature request here: BAM-5206 .

      That page also contains tips on how to roll out your own Windows image if you'd like to do it yourself.

  3. Malcolm McMahon

    Would't it be an idea to move to using an EBS root image, rather than an AMI?. They are significantly easier to tweak and the bamboo-ebs mount would, I think, be rendered unecessary.

    The start up script on my bamboo-ebs mount is making all kinds of changes to the root filesystem anyway and it's getting messy.

    1. Przemek Bruski

      We will most likely supply both image types at some point.

  4. Anonymous

    Where would one find the AMI IDs for each version of Bamboo?

      1. Anonymous

        I am running the AOD Bamboo on a trail version. I don't see the Windows default in my "Manage Elastic Image Configurations," window. Is this because the 30 day trail only allows one image?

         

        1. Przemek Bruski

          Atlassian OnDemand is presently using version 3.0 of Bamboo, where the Windows image wasn't available. I think there's a Bamboo@AOD upgrade coming in February.

          Normally, upgrades happen faster, but this one got delayed due to some JIRA/Crucible interdependecies.

          1. Anonymous

            Thank you.

            Do you know if that is early or late Feburary. I only ask because I was thinking I might go through the grueling process of creating a Custom Elastic Image and then installing MSBuild on it and then run my builds.

            I guess I will do it anyway. Might as well bite the bullet and learn something new.

             

            1. Przemek Bruski

              You need to contact OnDemand support to get a more precise date. I don't think it has been made public already.

              The process of creating custom images has been made much simpler in newer Bamboo versions, so you may want to wait a bit if it's just weeks away.

              1. Anonymous

                Hello Przemek,

                First thanks for answering all my previous questions.

                After 2 days of struggling getting the custom elastic image setup on Windows Server, and it not running properly. I've given up on Bamboo OnDemand doing MSBuilds.

                What I want to do now is keep our AOD (jira, confluence, etc...) and tie our atlassian.net SVN repository to point to Bamboo 3.4 hosted on a local windows box.

                Is that possible?

                Thanks,

                Rod

                 

                1. Przemek Bruski

                  There should be no problems with accessing your  .net SVN account.

                  If you encounter any problems with integration of standalone Bamboo with AOD, let us know via support.atlassian.com and we'll see if they can be sorted out.

  5. Anonymous

    I can start the stock Windows elastic machine but I cannot get into it? I would like to make an image out of it and customize my image. How can I get into this machine?

    1. Przemek Bruski

      When you enter the instance page on your Bamboo, it should display the Administrator password for that instance. Then just log in via RDC. More on customisation here: http://blogs.atlassian.com/2011/12/bamboo-amazon-ec2-windows/ and here: http://blogs.atlassian.com/2011/12/bamboo-amazon-ec2-windows-part2/ . Apologies for the resized screenshots, someone seems to have done something wrong with Wordpress configuration.