Bogus failures on ovirt-engine-master-check-patch
Hi guys, This job seems to be failing and interfering with our ability to work. Can you take a look please? E.g.: http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc22-x86_64/195... -Allon
Automation scripts should go into their own repo, their release cycle is different than the component, tags/branches/versions are separate. Adding these was a mistake and misunderstanding, as CI life cycle and versioning is detached from component, for example upgrade CI while maintaining old branches. If you do not like single repo for all automation script you can have xxxx-ci repo for these. But they should not be in package source repository. ----- Original Message -----
From: "Allon Mureinik" <amureini@redhat.com> To: "infra" <infra@ovirt.org> Sent: Tuesday, August 18, 2015 3:47:39 PM Subject: Bogus failures on ovirt-engine-master-check-patch
Hi guys,
This job seems to be failing and interfering with our ability to work.
Can you take a look please?
E.g.: http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc22-x86_64/195...
-Allon
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--6WlEvdN9Dv0WHSBl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 08/18, Alon Bar-Lev wrote:
=20 Automation scripts should go into their own repo, their release cycle is = different than the component, tags/branches/versions are separate. Adding t= hese was a mistake and misunderstanding, as CI life cycle and versioning is= detached from component, for example upgrade CI while maintaining old bran= ches. =20 If you do not like single repo for all automation script you can have xxx= x-ci repo for these. =20 But they should not be in package source repository.
I'm sorry, but I totally oppose that view. This issue is not caused by the = CI infrastructure, but because that patch has not been rebased in quite some t= ime and it does not include yet the patch that adds the proper script. As I see it is a totally ok error that it should and has been found by the = CI system. @allon, please rebase your patch
=20 ----- Original Message -----
From: "Allon Mureinik" <amureini@redhat.com> To: "infra" <infra@ovirt.org> Sent: Tuesday, August 18, 2015 3:47:39 PM Subject: Bogus failures on ovirt-engine-master-check-patch =20 Hi guys, =20 This job seems to be failing and interfering with our ability to work. =20 Can you take a look please? =20 E.g.: http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc22-x86_6= 4/195/console =20 =20 -Allon =20 _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra =20
Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--=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 --6WlEvdN9Dv0WHSBl Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJV0zCDAAoJEEBxx+HSYmnDcXsH/iyQAWWiLOyMF2MPYwwHd1SN 4KsgeQ5Zp91p0Kw2khjaKZJLNMoSzMNSsyk7EDwB4GAwnzEmRnHCM50VMCqDMZRP a2upFmMpk1ywXfuBWBtS9FFqP9DHp+azFSbpbvh09cFkYBhZ90IpYXNVL0/jh2MV TUKjapDX5soLBu5uSKFlZfceELUclSneZPVwB0hIsrXPuo5ZFTzN8L8+uTbyn3Bx RJOU5PAWcw8aQzZ1b63rBbW0kJ25HksmIA1XBvMjyGHe/QBSIu8iwoFDV3I3EIXc b/Ka6lZpwNmbVLBNzY9y/RD5Y0bwqqg3zY7P/4ZQCCAVoT9VlOyc63Koumvuf4I= =Grt6 -----END PGP SIGNATURE----- --6WlEvdN9Dv0WHSBl--
participants (3)
-
Allon Mureinik -
Alon Bar-Lev -
David Caro