Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Git checkout label checks out old commit

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?

1 answer

0 votes

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.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events