Re: [ovirt-devel] Gerrit parallel patch handling and CI (Or, why did my code fail post-merge)

----- Original Message ----- Thanks, I've missed that thread. So before we adopt auto-submit-after-ci-pass (e.g. using Zuul, as Eyal mentioned in that thread), we should be able to manually trigger heavy CI (check-merged) job from Gerrit web interface, is that correct? If so, it would be the patch owner's responsibility to submit (merge) only after heavy CI (check-merged) pass? As for Gerrit's "Submit" button hook, there's "pre-merge validation": https://gerrit-review.googlesource.com/Documentation/config-validation.ht... https://github.com/gerrit-review/gerrit/blob/master/gerrit-server/src/mai... This validation API (MergeValidationListener) doesn't seem async as it relies on exception (MergeValidationException) to block the operation. So we could actually write Gerrit plugin using MergeValidationListener that would operate in the following way: 1, on first "Submit" button click, tell Jenkins CI to run check-merged and block merge (e.g. providing reason like "wait till CI finishes") 2, Jenkins CI is expected to set some flag on patch once it finishes 3, on next "Submit" button click, block unless flag has "ok" value