Re: Separate notifications from list messages?

["Daniel P. Berrangé" <berrange@redhat.com>]

On Fri, Jul 10, 2020 at 09:32:28AM +0100, Peter Maydell wrote:
> On Fri, 10 Jul 2020 at 09:25, Liviu Ionescu <ilg@livius.net> wrote:
> >
> >
> >
> > > On 10 Jul 2020, at 11:09, Peter Maydell <peter.maydell@linaro.org> wrote:
> > >
> > > What sort of notifications are we talking about here ?
> >
> > For example:
> >
> > ...
> > Received: from mg.gitlab.com (74.90.74.34.bc.googleusercontent.com
> >  [34.74.90.74]) by smtp-out-n18.prod.us-west-2.postgun.com with SMTP id
> >  5f074fb9a33b1a3dd4571072 (version=TLS1.3, cipher=TLS_AES_128_GCM_SHA256);
> >  Thu, 09 Jul 2020 17:11:21 GMT
> > Date: Thu, 09 Jul 2020 17:11:20 +0000
> > Message-ID: <5f074fb827f26_7cd93fa34d371dbc1570d@sidekiq-catchall-02-sv-gprd.mail>
> > Subject: QEMU | Pipeline #164899134 has failed for master | 3d7cad3c
> > Reply-to: GitLab <noreply@gitlab.com>, GitLab <gitlab@mg.gitlab.com>
> > From: GitLab via <qemu-devel@nongnu.org>
> > ...
> 
> Thanks; yeah, I've seen those go past. Do we expect any other
> kinds to appear as we make more use of gitlab?

This was an explicit configuration choice to make the CI failure reports
appear on the list, rather than expecting one or two people to be
responsible for watching the CI. IME if we move them off to a separate
list in practice almost no one will bother to subscribe to the list.

Ideally we would not have any failures in the first place, but right now
GitLab CI is done post-merge.

When Peter starts using GitLab CI as one of the pre-merge gates, then we
should see very few CI failure messages on list. We'll likely still get
a few due to transient infrastructure problems. I think this is the
important thing to focus on here, rather than trying to hide away the
current CI failures.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|