|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

This is not critical issue since only caused in rare condition. But it would be critical if once happens.
From code, It is certain that gerrit-trigger runs under the below assumptions:
The event instance generated by Gerrit event stream is different with the one generated by manual trigger. But object comparison by equals() is true. This fact breaks assumption #1.
If manual trigger happens while triggered job has running build triggered by Gerrit stream event, a job has 2 builds generated by the same event. This breaks assumption #2.
So when manual trigger happens, plugin behavior is already unstable. Unfortunately, result would be undefined.
Perhaps this is design issue. So this cannot be fixed easily with no plan.