Hi Folks,
Thanks to the CentOS CI project[1], we have automated build jobs running on
every libvirt change. Currently each job is spamming a selected set of
email addresses. It seems we're doing a general poor job of actually
dealing with breakage though. For example the Mingw build of libvirt has
been reported broken for a month and a 1/2 :-(
I think it would be useful if we had a broader audience able to see
build failures across all the libvirt jobs. At the same time though I
dont want to force all libvirt developers to receive this spam. So I
suggest we should create a new mailing list 'libvirt-ci(a)redhat.com'
which is used to report all CI job failures. People can opt-in to this
mailing list to receive reports if they're interested in helping to
fix breakage when it happens. We'd set reply-to in the mailing list
to be libvir-list(a)redhat.com. IOW, libvirt-ci would be a read-only
mailing list for subscribers - any discussion about failures would
still be on libvir-list(a)redhat.com
Regards,
Daniel
[1] https://ci.centos.org/
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
Hi Folks,
Thanks to the CentOS CI project[1], we have automated build jobs running on
every libvirt change. Currently each job is spamming a selected set of
email addresses. It seems we're doing a general poor job of actually
dealing with breakage though. For example the Mingw build of libvirt has
been reported broken for a month and a 1/2 :-(
I think it would be useful if we had a broader audience able to see
build failures across all the libvirt jobs. At the same time though I
dont want to force all libvirt developers to receive this spam. So I
suggest we should create a new mailing list 'libvirt-ci(a)redhat.com'
which is used to report all CI job failures. People can opt-in to this
mailing list to receive reports if they're interested in helping to
fix breakage when it happens. We'd set reply-to in the mailing list
to be libvir-list(a)redhat.com. IOW, libvirt-ci would be a read-only
mailing list for subscribers - any discussion about failures would
still be on libvir-list(a)redhat.com
Sounds good to me. I would certainly be likely to monitor it more than
now.
On Fri, Jul 01, 2016 at 02:04:57PM +0200, Martin Kletzander wrote:
> On Fri, Jul 01, 2016 at 11:44:54AM +0100, Daniel P. Berrange wrote:
> >Hi Folks,
[...]
> Sounds good to me. I would certainly be likely to monitor it more than
> now.
+1