jenkinsci / jenkinsci/gerrit-trigger-plugin

[JENKINS-31167] Gerrit Trigger: every build has all commits listed in the Changes page

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

Description

I configed the Gerrit Trigger plugin on jenkins based on the article https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger.

On git plugin, I set Refspec to refs/changes/*:refs/changes/* and 'Branches to build' to $GERRIT_REFSPEC.

The job can be triggered whenever new patch set is created. However, the changes to this build contains all the changes (can show max to 1024 changes in total).

This issue bothers me a lot because I'm supposed to send email only to the committer instead of sending emails to all the people contributing to that changelog.

Same issue happened in this url: https://groups.google.com/forum/#!topic/jenkinsci-users/KKITzpqG5_s

---
Originally reported by winnerwbx, imported from: Gerrit Trigger: every build has all commits listed in the Changes page


  • assignee: rsandell
  • status: Open
  • priority: Critical
  • component(s): gerrit-trigger-plugin
  • label(s): changelog, gerrit-trigger, git-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 3
  • imported: 2025-12-06

Raw content of original issue

I configed the Gerrit Trigger plugin on jenkins based on the article https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger.

On git plugin, I set Refspec to refs/changes/*:refs/changes/* and 'Branches to build' to $GERRIT_REFSPEC.

The job can be triggered whenever new patch set is created. However, the changes to this build contains all the changes (can show max to 1024 changes in total).

This issue bothers me a lot because I'm supposed to send email only to the committer instead of sending emails to all the people contributing to that changelog.

Same issue happened in this url: https://groups.google.com/forum/#!topic/jenkinsci-users/KKITzpqG5_s

environment

```
Ubuntu 14.04.3 LTS

Jenkins ver. 1.634

Gerrit Trigger 2.16.0

GIT client plugin 1.19.0

GIT plugin 2.4.0

java version "1.7.0_79"

Gerrit Code Review version: 2.10
```

3 attachments

- [2015-10-26_meitu_2.png](https://issues.jenkins.io/secure/attachment/30944/2015-10-26_meitu_2.png)
> ![2015-10-26_meitu_2.png](https://issues.jenkins.io/secure/attachment/30944/2015-10-26_meitu_2.png)
- [2015-10-26meitu_1.png](https://issues.jenkins.io/secure/attachment/30943/2015-10-26meitu_1.png)
> ![2015-10-26meitu_1.png](https://issues.jenkins.io/secure/attachment/30943/2015-10-26meitu_1.png)
- [2015-10-26meitu_4.png](https://issues.jenkins.io/secure/attachment/30947/2015-10-26meitu_4.png)
> ![2015-10-26meitu_4.png](https://issues.jenkins.io/secure/attachment/30947/2015-10-26meitu_4.png)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue with the reported Gerrit Trigger, Git plugin, Git client plugin, Jenkins, and Gerrit versions, using the stated refspec and $GERRIT_REFSPEC configuration. Compare the build's Changes page with the newly created patch set; done means the page lists only the relevant changes rather than all available commits.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
ci-cd, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.