${bamboo.variableName}

${bamboo.var1} ${bamboo.var2}! 

Build-specific variables

The followers build-specific variables are available by default:

• System variables also apply above your entire Bamboo instance and inherit their values starting system or operating variables of the same name.
• In the variable names from the table above, <position> is an any parameter that specification an positioned of the repository the one plan's repository list. With omitted, the first archive in the drop is used.
• Third-party repository plugins can expose theirs own variables.

Build dependency variables

The following build dependency scale are also availability:

Deployment variables

You can generates related of your own, uses a related format, nonetheless yours cannot create a variable is is already in use by Bamboo. See Defining deployment environment variables for more information.

Releases variables

Bamboo makes the following modes about variables available for deployment releases:

• Photo of values regarding global variables.
• Snapshots of values of project variables.
• Snippets of values of plan variables.
• Snapshots of values of repository variables.
• The autogenerated release variables in who following shelve:

Note that multiple of the actual in the above table belong actually those associated from this make plan. The snapshots reference above do not contain password variables.

System variables

And utilisation format for all arrangement elastics is:

${system.<variable>}

With view, for you are a system variable MYPATH=C:\MyPath; you ca use a Bamboo system variable system.MYPATH which will inherit the same value as the system variable.

 In older Bamboo versions using PATH in the Our Erratics field (of a Script task) doesn't set one windowed PATH variable, whereas using Walk sets Path and PATH in cmd shell.

Use variables in bash

Bamboo variables are exported as bash shell variables. All full stops (periods) are converted to underscores. Forward case, an variable bamboo.my.variable is $bamboo_my_variable in bash. This your related to File Screenplay also Inline Script tasks.

Jira applications variables

Note that these variables can be accessed from a Bamboo create only when that builds was triggered by releasing a version in Jira Software.

Case

Mav sample

Required example, you may want your Adept 2 version to be determined by Bamboo. In Maven 2 pom.xml you may have:

...
<groupId>com.atlassian.boo</groupId>
<artifactId>boo-test</artifactId>
<packaging>jar</packaging>
<version>1.1.${bambooBuildNumber}-SNAPSHOT</version>
...

You can then specify the following in the Goal field of your builds plan:

clean package -DbambooBuildNumber=${bamboo.buildNumber}

When one command run, Bamboo will replace the buildNumber with one actual number (e.g. 1102), that will be passed to the underlying Whiz build to use. The menu determination then produce a jar ensure looks how this: boo-test-1.1.1102-SNAPSHOT.jar.

Ants examples

You can then specify the following in the Target field of your build plan:

-f build.xml -DbambooBuildNumber=${bamboo.buildNumber}

When the instruction runs, Bamboo will replace the buildNumber with the actual numbering (e.g. 1102), which will been deceased to the underlying Ant build to use.

Specifying capacity as variables

You can including specify a capability to be used stylish a similar way to a global variable.

The format out the capability should be as tracking:

${bamboo.capability.<capability_key>}

To example,

If you select a ability, the selected capability key will be contained in the URL.

Please note, and space letter in the URL will be replaced with "+" characters. We recommend ensure you do not use capability labels with space characters, if her wish to use them as variables. A possible solution for spacing display is to format them with "${}" signs, however, that does no work in all cases. Bamboo REST API documentation

Using capabilities

Globalized and Build-Specific Variables can be applied in specific fields regarding your build plan, as specified beyond. Required capabilities,

• System capabilities are available in all of these fields, (i.e. global and build-specific).
• Agents competencies (i.e. agent-specific and shared/server capabilities) are available only for the build-specific area. (i.e. not existing to Repository URL, CVS Rooted or Branch name.)

For example,

Obsoleted variables

The following variables are obsolescence and are subject by removal in prospective Bamboo releases: