To me argument of having info that server failed vs have cleaned inbox finally - I'm choosing to have inbox cleaned.
If Apache rejected email from Jenkins on commits@ I can ask infra what can be done. On Mon, Apr 20, 2020, 10:43 PM Alex Harui <aha...@adobe.com.invalid> wrote: > I've been unable to get the CI server to send to commits@. Apache blocks > it. > > Maybe issues@, but these aren't about issues. > > IMO, the point of these Jenkins emails is so that all committers know the > current state of the builds and help fix issues when possible. My concern > is that when committers start filtering CI emails they will miss when one > of their commits breaks the build. So, the only reason to split CI emails > off this list is to reduce traffic to the non-committers. > > My 2 cents, > -Alex > > On 4/20/20, 1:17 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > > We already have issues@ and commits@. Can we redirect the emails to > one of > the lists? > > On Mon, Apr 20, 2020 at 11:54 AM Alex Harui <aha...@adobe.com.invalid> > wrote: > > > IMO, if we do create a new list, all committers must be subscribed. > > > > My 2 cents, > > -Alex > > > > On 4/20/20, 1:53 AM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com> > wrote: > > > > Hi Guys, > > > > In the last year or so all notifications from Jenkins build are > going > > to > > development mailing list. It becomes very messy I see every day > 40-50 > > emails where 80% of that is notification from Jenkins. > > > > I would like to propose create separate mailing list to have such > > notifications there. > > > > Is it possible? > > > > Please share your thoughts on that subject. > > > > Thanks, > > -- > > > > Piotr Zarzycki > > > > > > > > >
