On Tue, Jun 16, 2015 at 08:48:17PM +0200, dcaro wrote:
On 06/16, Eyal Edri wrote:
Sounds like a bug. Jenkins should only use the CI flag and not change CR and V flags. =20 Might have been a misunderstanding. David, can you fix it so Jenkins will only update CI flag? =20 Can someone pass me an example of the patch that had the reviews? It's =
--e5bfZ/T2xnjpUIbw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I just rolled out the CI flag to all the projects this morning, restricting jenkins to set only that flag, did that happen again after it? On 06/17, Dan Kenigsberg wrote: possible
that previously the jobs were manually modified to only set the ci flag= and we updated them on yaml and the manual changes got reverted. Having a samp= le patch would allow me to trim down the list of possible jobs that give that re= view. =20 =20 That can be prevented globally easily, but until all projects have the = ci flag we can't enforce it globally. =20 See for example https://gerrit.ovirt.org/#/c/42362/ =20 Patch Set 5: Code-Review+1 Continuous-Integration+1 Verified+1 =20 in a later run seems to have fixed this =20 Patch Set 6: Continuous-Integration+1
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --e5bfZ/T2xnjpUIbw Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVgXCwAAoJEEBxx+HSYmnDpKkH/itc1DQ/icdP0hiydK7fh3Tp EdeVitya4uiGuTGzETxVPFnnxNCqZaCzLf2GmXez5b7Fu0SNnJ2QjwnyPKvDVIid TO3GETUtO9SdXPA0eOc0fO8QFIW0LYx44R9OYog49hrBxjrQWY6CHQJ+AOF/ldGj AQl7D7AGQ8drYQP2NT4MlLYTuKJwX+IV9EuhhSbFCXf0Gn0KlSBewiPkJdc8Jm7p ntCzhHKlbfgbqjvg53woo+ovIbg4DCyreXWyf7m2J4J5QuqxSLmmS9sCB7p4UiGM 91K8Y0av6z6XUSEgjcCpCnufAZn6f8T/9ZYpdpl0GqcWs/KY8OIxx81g1q3B3LU= =fk+B -----END PGP SIGNATURE----- --e5bfZ/T2xnjpUIbw--