jenkinsci / jenkinsci/gerrit-trigger-plugin

[JENKINS-38675] gerrit trigger git summary show refspec instead of branch

Open
#803 4 comments 0 reactions 0 assignees View on GitHub
component:gerrit-trigger-plugin enhancement imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
226
Forks
289
PR merge metrics
No merged PRs in 30d

Description

When you have multiple git projects in a pipeline build, multiple git summary bits appear in the build information when you highlight the build. These currently show something like

Revision:



  • a built branch

  • another built branch

When using the gerrit trigger plugin, the "built branches" only show the name of the branch from $GERRIT_BRANCH, instead of showing a refspec. Ideally when using these together, we should see the refspec instead of the branch because this is really what was built by the job.

---
Originally reported by jekeller, imported from: gerrit trigger git summary show refspec instead of branch


  • assignee: rsandell
  • status: In Progress
  • priority: Minor
  • component(s): gerrit-trigger-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 3
  • imported: 2025-12-06

Raw content of original issue

When you have multiple git projects in a pipeline build, multiple git summary bits appear in the build information when you highlight the build. These currently show something like

<git image> Revision: <sha1id of checked out source>



  • a built branch

  • another built branch

When using the gerrit trigger plugin, the "built branches" only show the name of the branch from $GERRIT_BRANCH, instead of showing a refspec. Ideally when using these together, we should see the refspec instead of the branch because this is really what was built by the job.

Contributor guide

Open the contributing guide

Research direction

Start by tracing how the gerrit-trigger-plugin handles GERRIT_BRANCH and how the Git summary is produced for pipeline builds; the payload names no files or tests. Confirm the current display with multiple Git projects, then make the built-branch summary show the refspec used by the job and verify the result with the repository's existing tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, java
Domain
ci-cd, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.