[JIRA] [gerrit] (JENKINS-24445) Retriggering builds via the "Manual Trigger" feature of the Gerrit Trigger Plugin causes wrong verification

[rinrin...@gmail.com (JIRA)]

rin_ne edited a comment on JENKINS-24445 Retriggering builds via the "Manual Trigger" feature of the Gerrit Trigger Plugin causes wrong verification I reproduced this on the latest plugin code but there is a bit difference with what you mentioned. UPDATE: The below results are in condition: jobs has one completed build as "#1". So "#2" is triggered build by event, "#3" is triggered build by manual trigger. This will let Test_2 finish successfully (as Test_2 always succeeds). The bug that happens now, is that the trigger plugin uploads a "Verified +1" message, DESPITE "Test_1 #2" not yet being finished. When LOCKFILE_Test_2-3 was removed, any message was not uploaded. Next, LOCKFILE_Test_1-2 was removed. Then message "Verified -1" was uploaded from "Test_1 #2". Also message "Verified +1" was uploaded when LOCKFILE_Test_2-2 was removed. Finally, LOCKFILE_Test_1-3 was removed. Then message "Verified -1" was uploaded with verdict value both "Test_1 #3" and "Test_2 #3". It means that uploading message for "Test_2 #3" was pended until "Test_1 #3" is completed. It means that: Running builds for event from Gerrit were deviated from verdict logic by manual triggered ones. But these were still enabled as individual triggered build. So I think that the issue you should address is #2. right?

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.