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