Git checkout label checks out old commit

[schow-lmi3d]

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?

[Daniel Santos]

Hi @schow-lmi3d

That is really strange. Bamboo should see exactly what is stored in the remote git repo.

• Is it possible that the tags update was not transferred to the remote?

  git push --follow-tags

• What happens if clone this repository again and try to checkout for that tag, will that work as expected?
• Have you tried a checkout using a script task Bamboo?

If you cleaned the cache in Bamboo, I don't see any reason for this checkout to be referencing the wrong commit.