nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to use a Jira version number in a Bamboo build

Simon Inglis

Howdy,

I'd like to paramatarize my Bamboo builds so that a Jira version number is available in the build to assist with packaging.

For example, In Jira I have a version of '1.1'. I'd like my build.xml use that version number and the bamboo build number the naming of the artefacts. For instance naming my release tar file as 'product-<jira version>.<bamboo build>.tgz'

Thanks,

Simon.

Accepted answers

Jens Schumacher2

When using the JIRA Bamboo plugin and it's release management capabilities, you will have access to the JIRA version as a Bamboo variable.

The following variables are available when the build gets triggered by a JIRA release:

${bamboo.jira.baseUrl}

${bamboo.jira.projectKey}

${bamboo.jira.projectName}

${bamboo.jira.version}

${bamboo.jira.username}

All comments

ReneR

You can set a Plan variable ahead of time:

http://confluence.atlassian.com/display/BAMBOO/Using+Global%2C+Plan+or+Build-specific+Variables

Or set the value as you run the build in 'paramaterised' mode:

http://confluence.atlassian.com/display/BAMBOO/Triggering+a+Plan+Build+Manually

Jens Schumacher2

When using the JIRA Bamboo plugin and it's release management capabilities, you will have access to the JIRA version as a Bamboo variable.

The following variables are available when the build gets triggered by a JIRA release:

${bamboo.jira.baseUrl}

${bamboo.jira.projectKey}

${bamboo.jira.projectName}

${bamboo.jira.version}

${bamboo.jira.username}

Andrew Benz3

Does the entire build need to be triggered by JIRA to get these variables? I have a build that has four stages, the last of which is a manual stage that I was to trigger from the JIRA release function. I only want to use the JIRA variables in the last stage, but when I triggered the manual step from JIRA, it looks like that variable was not picked up and ${bamboo.jira.version} was left alone while ${bamboo.buildNumber} was replaced correctly.

Timothy Marks1

I am struggling with the exact same behavior... (Bamboo 4 and Jira 5)

Ron Chan2

Jens - we're on Bamboo 5.6 and JIRA 6.3, would this answer still be relevant? or what should be expected now? As I recall, there's still a pending issue with "JIRA release triggering build", being that you cannot select the branch you wish to release...which is essentially a showstopper. Any help would be appreciated! Regards, Ron