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.
G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events