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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,559,412
Community Members
 
Community Events
184
Community Groups

Plan variable updating in build is not reflected in next build

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
TAGS
AUG Leaders

Atlassian Community Events