You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have a global variable that I use to label and version builds in a plan.
Each build needs to have its own unique build number across all branches.
The plan uses the "Version Variable Incrementer" to increment this global variable at the beginning of each build. It has "Include global variables" checked, and is using the "Bamboo Deployment algorithm" increment pattern.
This is mostly working, except that every now and then the global variable will jump back to an earlier number, and I cannot work out why.
When I look in the audit log, I can see the global variable being created over and over again (rather than updated), e.g.:
Timestamp | User | Changed field | Old value | New value |
19:34, 3 Jul | SYSTEM | Variable [uBindBuildNumber] has been created. | 984 | |
19:30, 3 Jul | SYSTEM | Variable [uBindBuildNumber] has been created. | 983 | |
19:30, 3 Jul | SYSTEM | Variable [uBindBuildNumber] has been created. | 1006 | |
19:24, 3 Jul | SYSTEM | Variable [uBindBuildNumber] has been created. | 1005 | |
18:54, 3 Jul | SYSTEM | Variable [uBindBuildNumber] has been created. | 1004 | |
18:53, 3 Jul | SYSTEM | Variable [uBindBuildNumber] has been created. | 1003 | |
18:50, 3 Jul | SYSTEM | Variable [uBindBuildNumber] has been created. | 1002 |
I can't see any other uses of this variable, but we have a lot of plans so I may have missed something.
How can I work out what is going on?
(We are using Bamboo version 5.13.1 build 51315)