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
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.
im aware that the git revision is snapshotted at the start of a plan build, so between tasks it will be stable.
I however have a complex build pipeline built up between dependant plans that trigger each other.
When the first plan changes the git repo (and pushs) the second plan is triggered. you can see that second plan deep clones the repo (testing this way as it should work) and then checkout an old revision, not the branch that was set up in the definition of that repo for that plan.
I know the first plan has finished, and the git push has worked.
The second plan even tells you that you are at a detached head (not the selected branch definition that was chosen), adding a task that checks out the branch again fixs the issue.
This is a real pain, I guess there is some form of timing issue going on, it could be the gitlab server, or bamboo to be honest (no idea). but this timing window does seem quite large (i.e. time between plans)
anybody know a different way to fix this issue, it would be nice to have a feature to disable the snapshot of commit ids if this is the consequence.