12:12 p.m.
--6c2NcOVqGQ03X4Wi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 12/09, Oved Ourfali wrote:
What happens when rebasing?
We can't afford waiting for tests to run on each rebase... as we might en=
d up
rebasing forever.
For now we will have to, all the code that is going to be merged must
be tested as it is going to be merged, that means running the tests in
the last rebase too.
In the future there are plans on using a gating system like zuul, so
zuul will be the one monitoring the tests and merging when passes, so
you will just add the flag, and that will trigger the gate, that runs
the tests and merged the patch.
It's unlikely that you'll have to wait forever, but there's nothing
avoiding you doing that (right now even).
I'd like to put emphasis again on differentiating between tests that
are fast, that should run on each patch and tests that are slow, that
should run on each merge. That will improve the feedback times.
=20
----- Original Message -----
> From: "David Caro" <dcaroest(a)redhat.com>
> To: devel(a)ovirt.org, infra(a)ovirt.org
> Sent: Tuesday, December 9, 2014 11:43:04 AM
> Subject: [ovirt-devel] Creating a new gerrit flag
>=20
> Hi!
>=20
> e have been having an issue with gerrit patches being merged before
> jenkins ran any tests on them, to avoid it from happening again I
> propose creating a new gerrit flag (Tests) with the following
> specifics:
>=20
>=20
> +1 - Tests passed/overrided
> 0 - Tests pending
> -1 - Tests broken
>=20
> where +1 is required to submit, +1 is set by jenkins when
> passing the tests and -1 is set by jenkins in case it breaks any
> tests. The +1 flag can be set also by maintainers to allow overriding
> the process.
>=20
> That way all the tests will be blocked until someone (hopefully
> jenkins) adds the +1 flag, but if the maintainer wants to override the
> value, she just has to set that flag herself.
>=20
>=20
> What do you think?
>=20
>=20
> --
> David Caro
>=20
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R&D
>=20
> Tel.: +420 532 294 605
> Email: dcaro(a)redhat.com
> Web: www.redhat.com
> RHT Global #: 82-62605
>=20
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
--=20
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605
Email: dcaro(a)redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
--6c2NcOVqGQ03X4Wi
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJUhssDAAoJEEBxx+HSYmnDlmAH/jTGLANAfsNTi8QkXiDHONor
Ye6SDEmj4Wz77VvFEskba9GDvCjKYUs9yf1dCI+ETba4+ilvlu+M9foEe4x0bpK+
EeVrKUxHyAP+y0hKvUoK1IsNBboJtYLOQcnAjPKnTzgemzvNjhzG+GvUJCVbrmn0
o7Jd1WEE3uCnjEgOnP5V1M+7cP/w0w6pSNhoT0taAU+T3ftXLKBZWZHU5k/hLGwc
qSzUYWJlYeW9JYDa4Z0vsaxFUHuppYzpZI37oo7AR6ZoBobs/P+Se7fXUPfscEX3
5cCsM6De/1qZkdfB53b93LYn7VKxGwFAtULFunw5tWshlNb0wtBrupFnkaxmHuA=
=BxeC
-----END PGP SIGNATURE-----
--6c2NcOVqGQ03X4Wi--