Summary

It's not possible to read Bamboo global variables when executing code, as this would pose a security risk and expose internal information. This article covers workarounds to pass Bamboo variables to the builders.

Environment

All Bamboo versions, with Maven, Ant, or other builders.

Solution

Passing variables as parameters

Although Bamboo variables are not directly available in the builder execution context (Maven, Ant, etc.), they can be passed as parameters to the builder. Please refer to Passing Bamboo variables to a build script for steps.

    <groupId>org.springframework</groupId>
    <artifactId>gs-maven</artifactId>
    <packaging>jar</packaging>
    <version>0.1.0.${bambooVariableName}</version> 

clean package -DbambootribalTarget=${bamboo.VariableName}

gs-maven-0.1.0.myValue.jar

Environment variables

If you're using Maven or Ant as the build tool, it's possible to add environment variables to those apps, externally, and read them in the Java code. See Accessing Maven properties in Java and Ant: Using Environment Variables.

Script task

You can add a Script task that does and echo of the value of the Bamboo Global variable to a file, and then have your Java code read it from that file.
Since Bamboo Global Variables are available within Bamboo's tasks, the Script task would have access to the value and could be used to output it to the system, which could then be used by the Java code.

Shell variables

If your goal is to use the variable to name files build by the builder tools, you can also set a variable in a shell  script, and use it to rename the files manually.