----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "Greg Sheremeta" <gshereme@redhat.com> Cc: "David Caro" <dcaroest@redhat.com>, devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Tuesday, May 26, 2015 11:40:16 AM Subject: Re: [ovirt-devel] broken build list?
----- Original Message -----
From: "Greg Sheremeta" <gshereme@redhat.com> To: "David Caro" <dcaroest@redhat.com> Cc: devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Tuesday, May 26, 2015 6:25:08 PM Subject: Re: [ovirt-devel] broken build list?
----- Original Message -----
From: "David Caro" <dcaroest@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Greg Sheremeta" <gshereme@redhat.com>, "infra" <infra@ovirt.org>, devel@ovirt.org Sent: Tuesday, May 26, 2015 11:22:33 AM Subject: Re: [ovirt-devel] broken build list?
On 05/26, Sandro Bonazzola wrote:
Il 26/05/2015 17:03, Greg Sheremeta ha scritto:
Any interest in creating a "broken build" list?
I frequently run across jobs failing (findbugs, upgrade, etc.) that aren't related to the patches I post, and I'm never sure whether the responsible person knows about it, whether it's being worked on, etc. I think many of us feel that way -- and, most times, we just wait and try again later.
The idea is that all broken builds can be posted about on this dedicated list for higher visibility and knowledge. Then we can be more proactive about fixing them.
Can't we use infra@ for build failing on infra issues and devel@ for the real issues?
I thought we already were doing that :S
IMHO, there is way too much noise on infra.
i think last time we requested that any error that is unjustified to be reported to infra, so we can handle it. sure, we might not be able to handle any issue right away, but only if we'll have the issues reported we can start mitigating things.
the last thing we'd like is to people not to trust ci and ignore errors...
I can't speak for everyone, but when I see one of my builds fail, my first thought is that someone else broke it. Maybe I need to check my ego, haha :)
bad for everyone.. if regressions will go in due to noise.
take into account that the environment isn't hosted on a perfect environment isolated from the world, any network issue with external repositories or slow gerrit response might fail jobs, we're working hard to eliminate those as much as possible.
i suggest that any issue you think is not related to your patch and isn't a real issue ,report it to infra list with:
subject: [ TICKET ] short desc of the problem body: info on the problem with links and why do you think its
Ok, so if everyone will use infra this way, that is fine. I rarely see anyone reporting build issues. Thanks!
we'll accumulate the tickets and try to debug each issue according to capacity, we're in the process automating this via email to support and opening ticket in jira.
e.
Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme@redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- 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
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel