About merging patches without tests

[David Caro]

Hi!

From time to time we have some patches that are merged to master branches
without having been tested mostly because the developer merges before having any
response from the jenkins system.

Merging one of those patches makes any following test run on that branch to
fail, and creating a lot of noise and trouble around all patches and jobs.

So I wanted to stat a little discussion to bring up ideas on how to prevent
that. Some random thoughts:

* -1 the patch at jenkins job start, and reset to 0 on success or infra failure,
and keep -1 if jenkins failure
* Only send a message to the patch with 'jenkins jobs started'
* Setup zuul as gateway, and make it block the patches if they do not pass the tests



Cheers!
-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D

Email: dcaro at redhat.com
Web: www.redhat.com
RHT Global #: 82-62605

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20140515/ac046d2e/attachment.sig>