-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
Currently, for pipeline builds, every time the pipeline runs on a new node and merges the branch you're building with master, you get an extra "Git Build Data" entry in the sidebar, even though you're building exactly the same thing.
The individual screens show different revisions being built:
But actually, these are the same PR branch, merged with the same master branch. In this situation, I would expect a single entry, and I would expect the linked page to list the branches which were merged, not to show the commit hash of the merge result. The merge result is literally impossible to access after the build has completed anyway, so there is no point having this information at all.
Can you provide detailed steps to duplicate the problem?
The sample you've provided almost looks like multiple checkout operations are being performed (and I doubt that is what you're actually doing in your build).
Are the SHA-1 hashes in the git build data from the preceding builds? Since you indicate that the list continues to grow, it seems likely that they are somehow recording the history of the SHA-1's built by that job.
Is the job a Pipeline job or a Freestyle job?
If it is a Pipeline job, is it using a Pipeline shared library?