----- Original Message -----
From: "Mike Burns" <mburns@redhat.com> To: infra@ovirt.org Sent: Thursday, February 28, 2013 5:48:26 PM Subject: Jenkins alerts on infra list
I've noticed that the infra list has been somewhat inundated with Jenkins build failure notices recently. I wanted to ask whether infra is really the right place to get these notifications.
In some cases, I think that it is the right place, but in most, I think it's not.
Things like:
check_disk_space_on_jenkins_slaves check_gerrit_ovirt_org
and other jobs that are purely monitoring or slave maintenance jobs should report to infra.
Other jobs that are sub-project oriented, I think, should alert a sub-project specific mailing list:
ovirt-engine_create_rpms_fedora ovirt-engine_dao_unit_tests ovirt-engine-update_db_multiple_os etc...
While I think infra should know when there are service problems (like a machine's disk is full, or a service is down), I don't think it's worthwhile for infra to be alerted for *every* failure of a job in jenkins. It's not the job of infra to make other sub-projects fix their builds, just to provide the jenkins service.
I propose that all sub-project builds that send email to infra be diverted to the <sub-project>-patches mailing list.
Thoughts?
Basically i'm OK with that, it's just past experience showed that if some test is failing and missed by the relevant group (engine-patches gets way too many emails a day), then in the end this error will keep failing. maybe we can add emails to project maintainers as well for failing jobs, so they can nag the relevant committer who broke the build.
Mike _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra