About merging patches without tests

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --aRDxp1t8OJxB8Ou24htvVk9dCuM28RTPW Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi! =46rom time to time we have some patches that are merged to master branch= es without having been tested mostly because the developer merges before hav= ing 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= =2E So I wanted to stat a little discussion to bring up ideas on how to preve= nt that. Some random thoughts: * -1 the patch at jenkins job start, and reset to 0 on success or infra f= ailure, 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 pas= s the tests Cheers! --=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Email: dcaro(a)redhat.com Web: www.redhat.com RHT Global #: 82-62605 --aRDxp1t8OJxB8Ou24htvVk9dCuM28RTPW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" --aRDxp1t8OJxB8Ou24htvVk9dCuM28RTPW--