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

gerrit trigger does not deal with ref-updated very well

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When configuring the Gerrit Trigger to act on ref-updated Gerrit events on a push-direct branch (i.e. for a push to refs/heads/master rather than refs/for/master) it does not deal with multiple commit pushes very well.

      The Gerrit stream event looks like:

      {"type":"ref-updated","submitter":

      {"name":"John Doe","email":"john@example.com"}

      ,"refUpdate":{"oldRev":"a9...","newRev":"72...","refName":"FOO-1234","project":"foo"}}

      where there can be any number of actual commits between oldRev and newRev. The jenkins reporting for such a build is misleading in that it only lists 1 of the commits (can't remember if it was first or last) in the changelog. Further the "parameters" are also typically wrong. They seem to reflect the parameters for perhaps the previous job.

      I strongly suggest whoever is assigned this bug to actually try this use-case and reproduce the problem to see the various issues.

        Attachments

          Issue Links

            Activity

            There are no comments yet on this issue.

              People

              Assignee:
              rsandell rsandell
              Reporter:
              brian Brian Murrell
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: