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
I have a job that checks out a specific label from a repository, say V1. I had recently re-written history such that I had to relabel the V1 to the new rewritten history.
When I manually checkout the label ' git checkout V1', it checks out the new commit.
When I trigger the job, the job runs the command 'git checkout V1' but someone how it ends up checking out the OLD commit.
I've tried deleting the git cache but it still checks out the old commit.
Does anyone know why this is happening? How can I get the job to checkout the tag linked to the new commit?
That is really strange. Bamboo should see exactly what is stored in the remote git repo.
git push --follow-tags
If you cleaned the cache in Bamboo, I don't see any reason for this checkout to be referencing the wrong commit.