On 7/10/20 10:32 AM, Peter Maydell wrote: > On Fri, 10 Jul 2020 at 09:25, Liviu Ionescu <i...@livius.net> wrote: >>> On 10 Jul 2020, at 11:09, Peter Maydell <peter.mayd...@linaro.org> wrote: >>> >>> What sort of notifications are we talking about here ?
qemu-ci-notifications@ for all our CI? >> >> 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_7cd93fa34d371dbc15...@sidekiq-catchall-02-sv-gprd.mail> >> Subject: QEMU | Pipeline #164899134 has failed for master | 3d7cad3c >> Reply-to: GitLab <nore...@gitlab.com>, GitLab <git...@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? If we create qemu-ci-notifications@ we could enable the email notifications from Shippable/Cirrus/Travis. Shippable/Cirrus are only checked by Alex/myself, it is not practical. We could move the Travis-CI IRC notification to this mailing list. Then when jobs are ported to GitLab, we will simply disable the other CIs. But one unique list for all of them sounds a good idea, and let the developers the freedom to subscribe to it. Regards, Phil.
