Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-31167

Gerrit Trigger: every build has all commits listed in the Changes page

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • gerrit-trigger-plugin
    • 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

      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

        1. 2015-10-26_meitu_2.png
          2015-10-26_meitu_2.png
          52 kB
        2. 2015-10-26meitu_1.png
          2015-10-26meitu_1.png
          58 kB
        3. 2015-10-26meitu_4.png
          2015-10-26meitu_4.png
          146 kB

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

          Mark Waite added a comment -

          The mailing list seems to describe a configuration correction. Does that configuration correction also resolve this report?

          Mark Waite added a comment - The mailing list seems to describe a configuration correction. Does that configuration correction also resolve this report?

          Andy Wang added a comment -

          I did as the mailing list said: set Refspec to $GERRIT_REFSPEC, branches to $GERRIT_BRANCH and it didn't work for me. Then I changed the branch to origin/$GERRIT_BRANCH, it all worked. I guess that the $GERRIT_BRANCH only pass "master" to git plugin, and it need full branch name like origin/master.
          So problem solved but I think the plugin doc do need some correction.

          Andy Wang added a comment - I did as the mailing list said: set Refspec to $GERRIT_REFSPEC, branches to $GERRIT_BRANCH and it didn't work for me. Then I changed the branch to origin/$GERRIT_BRANCH, it all worked. I guess that the $GERRIT_BRANCH only pass "master" to git plugin, and it need full branch name like origin/master. So problem solved but I think the plugin doc do need some correction.

            rsandell rsandell
            winnerwbx Andy Wang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: