Alex, Yes problem is solvable - redirect email not to dev but to commits or other email which we have available - This is the solution.
If I'm new to the list and subscribing here - seeing tons of weird emails instead of emails about concrete subject - I would unsubscribe in about 1 day max. - I wouldn't care that I can make a filter on my inbox, cause I have for example 100 filters already. If I look into the archive I really cannot read it, cause mailing list is obfuscated by stuff which uses by PMC and committers - If you are PMC or committer and care about stuff you will subscribe for another list. Thanks, Piotr wt., 21 kwi 2020 o 08:44 Alex Harui <[email protected]> napisał(a): > I have a few minutes waiting for step 11 to finish so have some time to > think about this more. > > My understanding is that we would need to send from an a.o email address > to have it end up on commits@. I don't know how to do that on a shared > machine. > > Maybe we should agree on what the problem is before looking for > solutions. To me, the problem seems mostly unsolvable. As a PMC member > you are supposed to be watching the commits, and as a committer, you need > to know if you broke the build, and as a community member, you should help > fix the build even if you didn't break it. Moving CI emails out of your > inbox via another list or a filter certainly will save you time, but > doesn't seem fair to others. Because if you aren't doing your share of > commit reviews, or if you don't see right away that you might have broken > the build then others have more work to do or can't get their work done. > > And if we were a busier project, we might have rules on whether you can > commit while the build is broken or not so as not to make it harder for the > person trying to fix the build to fix it. > > But meanwhile, there are a lot of emails that you don't really need to > read. How can anyone know which ones to read and which ones can be > skipped? And what tools can be used to make that happen? Are there email > tools that can tell if someone is working on a broken build? Can Jenkins > tell us more in each failure message so you can filter out a series of > broken build emails? Maybe that's what we should be figuring out. > > My 2 cents, > -Alex > > On 4/20/20, 11:21 PM, "Piotr Zarzycki" <[email protected]> wrote: > > It's end up with using Dev, so I would like to get back to idea of > having > either separate mailing list or sending that to [email protected] - > Your > last comments indicates that email was still rejected - Is it still the > case ? > > wt., 21 kwi 2020 o 00:43 Alex Harui <[email protected]> > napisał(a): > > > I already asked. See: INFRA-15722 > > > > > > On 4/20/20, 2:45 PM, "Piotr Zarzycki" <[email protected]> > wrote: > > > > 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 > <[email protected]> > > 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" < > [email protected]> > > 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 > > <[email protected]> > > > 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" < > > [email protected]> > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Piotr Zarzycki > > Patreon: * > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ca1ae2823bf944c82ba6908d7e5bc4b5a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637230469193169564&sdata=7MpOVnN%2F5QbK2TF6o%2F%2FGY43wKTRTNYRBSE4MANdz5%2B4%3D&reserved=0 > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ca1ae2823bf944c82ba6908d7e5bc4b5a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637230469193169564&sdata=7MpOVnN%2F5QbK2TF6o%2F%2FGY43wKTRTNYRBSE4MANdz5%2B4%3D&reserved=0 > >* > > > -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki <https://www.patreon.com/piotrzarzycki>*
