Hi Rui,
The seed job being broken is sort of a big deal because it prevents
updates to our Jenkins jobs. However, it doesn't stop the existing test
configurations from running. I haven't found the mails annoying but I'm
ok with moving them to the builds@ list.
-Max
On 22.10.18 11:05, Colm O hEigeartaigh wrote:
We had a discussion recently about splitting the JIRA notifications to a
new list "[email protected]", and also splitting the Jenkins mails to
(potentially) "[email protected]". So I guess the issue you raised can be
done once the latter mailing list is set up and active.
Colm.
On Fri, Oct 19, 2018 at 11:29 PM Rui Wang <[email protected]
<mailto:[email protected]>> wrote:
Hi Community,
I have seen some Jenkins build failure/back-to-normal emails in dev@
in last several months. Seems to me that this setting is coded in
https://github.com/apache/beam/blob/master/.test-infra/jenkins/job_00_seed.groovy#L100.
In the link above, the comment says the seed job is very important
so the notification emails should be sent to dev@.
I am wondering if this is still true that we always want to see such
notifications in dev@? If such notifications have become spams to
dev@, can we move it to either commits@ or another dedicated
email address (maybe create a new one)?
-Rui
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
