Documentation for Bamboo 4.0.x. Documentation for earlier versions of Bamboo is available too.

Skip to end of metadata
Go to start of metadata

At least one JDK was automatically configured when you installed Bamboo 1. You can configure more by defining JDK capabilities.

You can define a new JDK capability for:

(info) Note that if an agent has its own specific JDK capability, the value will override the value of a shared JDK capability of the same name (if one exists).

Once you have configured a new JDK capability in your Bamboo system, its label (e.g. '1.5') will appear in the Build JDK list when you configure a job's builder (see Configuring tasks). The JDK you select will be used for every one of that job's builds. That is, the job can only be built by agents which have a JDK capability whose label is specified in the job's Build JDK field.

1 This depends on the system environment variables (e.g. 'JAVA_HOME=/opt/java/java_sdk1.5') that were present on the machine on which Bamboo was installed:

  • On the Bamboo server, environment variables that were present during installation were saved as shared local capabilities in Bamboo.
  • On remote agents, environment variables that were present during installation were saved as agent-specific capabilities in Bamboo.

3 Comments

Hide/Show Comments

  1. Dec 09, 2008

    Mads Nissen

    Any chance you'll add similar support for .NET Framework SDK 2.0 / 3.0 / 3.5?

    1. Dec 10, 2008

      Edwin Wong

      Hi Mads,

      Interesting idea. Out of the box, you can already use custom capabilities to manage .Net SDKs. So you can use that to control which builds run on which agents. Is this sufficient?

      Cheers,
      Edwin

  2. Dec 11, 2008

    Mads Nissen

    sure, that works. it only gives a slightly tilted perception when the JDK is natively supported and the .net sdk needs to be explicitly configured..