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

Gerrit Change Submit+Rebase created patchset but did not trigger a job

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: gerrit-trigger-plugin
    • Labels:
      None
    • Environment:
      Software Versions:

      Jenkins Master 2.164.3
      Gerrit Trigger Plugin 2.30.0
      Gerrit 2.16.5
    • Similar Issues:

      Description

      BEHAVIOR

      A change was rebased and submitted on our Gerrit server. This also created patchset number 14 for the change. But the jenkins job for this change was not triggered. It triggerred correctly for changes 1-13.

      EXPECTED BEHAVIOR

      Expected a job to be triggered in jenkins as we've configured it to trigger for all 'Patchset Created' events with no excludes.

      USER INVESTIGATION

      Gerrit UI Message

      We got this message shown in the Gerrit comments:
      Change has been successfully rebased and submitted as <REDACTED> by <REDACTED>

      Gerrit Plugin UI in Jenkins

      When I query the list of changes from the Gerrit plugin interface in jenkins I can see my change listed.

      Job Configuration

      I've also attached the job configuration for the gerrit trigger plugin.

      Logs

      I've verified in the Jenkins and Gerrit server logs that there were no exceptions/stacktraces around the time this change was merged. Also there was no reference to the last patchset anywhere in the logs.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              rsandell rsandell
              Reporter:
              sidguptajhs Siddhartha Gupta
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: