Hi, =20 we'd be more than happy to help and fix those issues. can you please provide links and info on specific failures so we can debu= g them? =20 also, you're welcome also to open a ticket to our ticketing system [1] to=
--OFj+1YLvsEfSXdCH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Also take into account that monday/tuesday we had a major outage on jenkins= and all the slaves behaved unreliably if working at all. On 02/05, Eyal Edri wrote: track a specific item.
keep in mind the infra team is limited in resources, so not all tickets m= ight be solves quickly, especially if a major outage (like we had this week) is in progress. =20 [1] https://fedorahosted.org/ovirt/newticket =20 /e =20 ----- Original Message -----
From: "Yevgeny Zaspitsky" <yzaspits@redhat.com> To: infra@ovirt.org Sent: Thursday, February 5, 2015 3:59:34 PM Subject: Jenkins failures =20 Hi All, =20 Lately I barely get any valuable input from the Jenkins CI builds on my patches. Throughout the last week most of the builds finished with diff= erent Jenkins failures. The reasons were: =20 =20 * git failure * lack of permission to mkdir * failure to retrieve artifacts from the artifactory * unexpected shutdown =20 Such a high rate of failures makes the value of the builds very low and causes me to spend my time on understanding whether it's my fault or no= t. =20 I'd be very thankful and happier if Jenkins reliability was improved. =20 Regards, Yevgeny =20 =20 * English - detected * English * Hebrew * Russian =20 =20 * English * Hebrew * Russian =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 --OFj+1YLvsEfSXdCH Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU03k3AAoJEEBxx+HSYmnDDGMH/3D8Fs0pYkZ7BULsQz+oq5ZX yXtQFaTaFxGS82c2QoIrVQivyCWtVFab46MH5zCCCBoyx7qW5RCfhKTKDxrvMvXX Mgko8EG7pXBMr4NW013NR5gzFSK2OoV8V3hMVpRZfpeC484yT09LrCyx7G7gmqHe ICbUoCNynJ/LF07FfaJ1hqbb8q/miFjmXkkO4LaBXsqC+K308woLpVPH4gQGUhOc 0pnjxn4t2zJi/So3qcazRW9s8FgXLq+a3WvOHP+Y1gQTQozymomSDaVqTQEYzKCj /Ss8qb518wZ5ULpUw7/trhg4VxC8VqfXbjakRvWo0kd2xKt802hQzS+sIBJREII= =VJBJ -----END PGP SIGNATURE----- --OFj+1YLvsEfSXdCH--