"Git Build Data" / Jenkins remembering previous refs when checking out code?

[Andy Coates]

Hi,

I'm trying to debug an odd issue with a repo checkout that appears to relate to Git Build Data and Jenkins remembering previous "builds".

When I look at the Git Build Data, I see a tag and branch along with a ref, and a build number in Jenkins from the activities in that job.  The job in this case was to merge an upstream repo, but it never got pushed back to origin.

Now when I run the same job and try to list origin/develop as the refspec for the origin repo it tries to check out a ref that doesn't exist anywhere (the ref of the merge from the previous job build that never got pushed).  It's like Jenkins saw the merge job succeed, and even though wasn't pushed, it's keeping track of that new ref in Git Build Data for that branch for origin/develop :(

How can I get Jenkins to checkout the latest origin/develop and not the one it _thinks_ was the latest "build"?  We're using containers for agents so its a brand new workspace each time, but it always checks out that Git Build Data ref it has for refspec origin/develop.

Thanks.