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?
Hi @schow-lmi3d
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.