jenkinsci / jenkinsci/git-plugin

[JENKINS-52926] "Git Build Data" should not appear more than once in the side menu for pipeline builds

Open
#3,334 15 comments 0 reactions 0 assignees View on GitHub
component:git-plugin enhancement imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
694
Forks
1.1k
Avg merge
1h 29m
Merged PRs (30d)
3

Description

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.

 

---
Originally reported by trejkaz, imported from: "Git Build Data" should not appear more than once in the side menu for pipeline builds


  • status: Open
  • priority: Minor
  • component(s): git-plugin
  • resolution: Unresolved
  • votes: 6
  • watchers: 10
  • imported: 2025-12-02

Raw content of original issue

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.

 

5 attachments

- [Screen Shot 2018-08-08 at 9.34.41 am.png](https://issues.jenkins.io/secure/attachment/43648/Screen%20Shot%202018-08-08%20at%209.34.41%20am.png)
> ![Screen Shot 2018-08-08 at 9.34.41 am.png](https://issues.jenkins.io/secure/attachment/43648/Screen%20Shot%202018-08-08%20at%209.34.41%20am.png)
- [Screen Shot 2018-08-08 at 9.34.50 am.png](https://issues.jenkins.io/secure/attachment/43647/Screen%20Shot%202018-08-08%20at%209.34.50%20am.png)
> ![Screen Shot 2018-08-08 at 9.34.50 am.png](https://issues.jenkins.io/secure/attachment/43647/Screen%20Shot%202018-08-08%20at%209.34.50%20am.png)
- [Screen Shot 2018-08-08 at 9.34.58 am.png](https://issues.jenkins.io/secure/attachment/43646/Screen%20Shot%202018-08-08%20at%209.34.58%20am.png)
> ![Screen Shot 2018-08-08 at 9.34.58 am.png](https://issues.jenkins.io/secure/attachment/43646/Screen%20Shot%202018-08-08%20at%209.34.58%20am.png)
- [image-2024-09-27-10-17-35-115.png](https://issues.jenkins.io/secure/attachment/63335/image-2024-09-27-10-17-35-115.png)
> ![image-2024-09-27-10-17-35-115.png](https://issues.jenkins.io/secure/attachment/63335/image-2024-09-27-10-17-35-115.png)
- [image-2024-09-27-10-19-43-914.png](https://issues.jenkins.io/secure/attachment/63336/image-2024-09-27-10-19-43-914.png)
> ![image-2024-09-27-10-19-43-914.png](https://issues.jenkins.io/secure/attachment/63336/image-2024-09-27-10-19-43-914.png)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.