-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Software Versions:
Jenkins Master 2.164.3
Gerrit Trigger Plugin 2.30.0
Gerrit 2.16.5
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.
[JENKINS-62527] Gerrit Change Submit+Rebase created patchset but did not trigger a job
Siddhartha Gupta
created issue -
Siddhartha Gupta
made changes -
| Description |
Original:
h2. 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. h2. 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. h2. USER INVESTIGATION h4. Gerrit UI Message We got this message shown in the Gerrit comments: Change has been successfully rebased and submitted as <REDACTED> by <REDACTED> h4. 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. h4. Job Configuration I've also attached the job configuration for the gerrit trigger plugin. h4. 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. |
New:
h2. 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. h2. 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. h2. USER INVESTIGATION h4. Gerrit UI Message We got this message shown in the Gerrit comments: Change has been successfully rebased and submitted as <REDACTED> by <REDACTED> h4. 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. h4. Job Configuration I've also attached the job configuration for the gerrit trigger plugin. h4. 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. |