Configuring a new JDK

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

You can define a new JDK capability for:

• a specific local agent — see Configuring an Agent-specific JDK Capability
• all local agents — see Configuring a Shared JDK Capability
• a specific remote agent — see Configuring an Agent-specific JDK Capability
• all remote agents — see Configuring a Shared JDK Capability

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 dropdown list when you configure a Job's builder (see Specifying a Builder). 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.

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