Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Plan variable updating in build is not reflected in next build

David van Luijk
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 21, 2022

We are updating a buildnumber using the Variable Updater plugin with the "maven-release-plugin 2.5 algorithm", which I would expect to generate a new number every time. Normally, we see this tracing passing by:

Set PLAN level variable PlanBuildCounter to new value 1439
Substituting variable: ${bamboo.PlanBuildCounter} with 1438

Apparently the newly incremented value is used only for the next build. I read somewhere that the value of plan variables is frozen during the build, but that is not an issue since each build still has its unique number. 

However, sometimes we see this tracing passing by:

Not touching variable PlanBuildCounter of type PLAN, as it's already 1432
Substituting variable: ${bamboo.PlanBuildCounter} with 1431

This seems to happen when the next build is queued directly after the current build, it almost seems as if the variable is frozen from the moment of queuing and not from the moment the build has started executing. Since we only use one build agent, there are no concurrent builds.

Has anyone experienced this behavior as well and know of a solution?

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events