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 can I set different bamboo variable value for automaticaly created branches (using regexp release/.+)

Libor Ondrusek

This question is in reference to Atlassian Documentation: Using plan branches

I have plan targeted to develop branch in git. In bamboo I set automatical creating branches for regexp release/.+

Develop branch I need build with maven profile dev but for all of releases branches need build with prod maven profile.

I have one bamboo variable with maven profile, which is set to dev for dev branches, prod for one master branch. When new release branch is created on bamboo, the variable is set to dev as in plan.

image2016-1-19 12:4:0.png

Accepted answers

Marcin Gardias

This might be not the simplest way but it might just work for you:

create script task that compares bamboo built-in variable ${bamboo.planRepositories.branchName} with the regexp
the script should create .properties file that defines proper maven target according to the comparison's result
you can then inject the properties from the file into the build using Variables Inject Task (bundled with Bamboo)
re-configure maven task to use injected variable.

All comments

Phill Fox

I would set a different release plan for production to the dev plans and follow the instructions on https://confluence.atlassian.com/bamboo/naming-versions-for-deployment-releases-361726798.html to set the naming convention for each.

Libor Ondrusek

I would to have only one plan for one component/library.

Libor Ondrusek

image2016-1-19 12:4:0.png

Marcin Gardias

This might be not the simplest way but it might just work for you:

create script task that compares bamboo built-in variable ${bamboo.planRepositories.branchName} with the regexp
the script should create .properties file that defines proper maven target according to the comparison's result
you can then inject the properties from the file into the build using Variables Inject Task (bundled with Bamboo)
re-configure maven task to use injected variable.

Libor Ondrusek

Thank you Marcin.

Your solution is little bit complicated but looks acceptable for me. I will try it.

Libor

Libor Ondrusek

Thanks.

It is working very well.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo

bamboo-administration

branch

plan