[JENKINS-54868] Display Organization/Project and Repository name(s) on the job details page · jenkinsci/git-plugin#3365

2018-11-26T20:21:58.000Z

Currently when checking out multiple repositories or a single repository with submodules the Git plugin only displays the commit sha(s) and branch name(s) for each of the repositories being checked out on the job details page and as part of the Git Build Data. It would be useful to have the Organization/Project and Repository name(s) displayed alongside the commit sha(s) and branch name(s). This makes it easier to associate the changes to the repository. --- Originally reported by tarungidwani , imported from: Display Organization/Project and Repository name(s) on the job details page status : In Review priority : Minor component(s) : git-plugin label(s) : configuration, git, newbie-friendly, pipeline resolution : Unresolved votes : 9 watchers : 13 imported : 2025-12-02 Raw content of original issue Currently when checking out multiple repositories or a single repository with submodules the Git plugin only displays the commit sha(s) and branch name(s) for each of the repositories being checked out on the job details page and as part of the Git Build Data. It would be useful to have the Organization/Project and Repository name(s) displayed alongside the commit sha(s) and branch name(s). This makes it easier to associate the changes to the repository. 5 attachments - [Jenkins.png](https://issues.jenkins.io/secure/attachment/50157/Jenkins.png) > ![Jenkins.png](https://issues.jenkins.io/secure/attachment/50157/Jenkins.png) - [image-2022-02-23-09-52-47-062.png](https://issues.jenkins.io/secure/attachment/57332/image-2022-02-23-09-52-47-062.png) > ![image-2022-02-23-09-52-47-062.png](https://issues.jenkins.io/secure/attachment/57332/image-2022-02-23-09-52-47-062.png) - [image-2022-02-23-10-53-35-405.png](https://issues.jenkins.io/secure/attachment/57335/image-2022-02-23-10-53-35-405.png) > ![image-2022-02-23-10-53-35-405.png](https://issues.jenkins.io/secure/attachment/57335/image-2022-02-23-10-53-35-405.png) - [image-2022-02-23-10-53-57-662.png](https://issues.jenkins.io/secure/attachment/57336/image-2022-02-23-10-53-57-662.png) > ![image-2022-02-23-10-53-57-662.png](https://issues.jenkins.io/secure/attachment/57336/image-2022-02-23-10-53-57-662.png) - [issue-img2.jpg](https://issues.jenkins.io/secure/attachment/45269/issue-img2.jpg) > ![issue-img2.jpg](https://issues.jenkins.io/secure/attachment/45269/issue-img2.jpg)

(31 comments) (0 reactions) (0 assignees)Java (1,088 forks)auto 404

component:git-pluginenhancementgood first issueimported-jira-issuepipelinepriority:minorresolution:unresolved

Repository metrics

Stars: (691 stars)
PR merge metrics: (PR metrics pending)

Description

Jenkins.png
image-2022-02-23-09-52-47-062.png
image-2022-02-23-10-53-35-405.png
image-2022-02-23-10-53-57-662.png
issue-img2.jpg

Contributor guide

Research direction: Investigate how Git Build Data is rendered in Jenkins job pages. Modify the relevant Jelly/HTML files to include the repository name from the checkout data. Test with multiple repositories and submodules.
Tech stack: java
Domain: backend
Issue type: Feature
Difficulty: 2
Estimated time: 1-2 days
Activity status: Active
Clarity: Clear
Prerequisites: JavaJenkinsGit
Newbie friendliness: 80

Repository metrics

Description

Contributor guide

Get fresh easy issues in your inbox.