Re: Jenkins emails

I would be cautious here. We should tackle the problem from the standpoint of reducing amount of failures, not whom we send emails to (that should be scoped too though). I believe that sending email to the person who might have broke the build is a good tool. --Mikhail Have feedback

Re: Jenkins emails

The failure emails are so frequent that they've just become noise to me. I'm +1 for not mailing individuals. I would also be in favor of sending them to commits@ instead of dev@. Andrew On Wed, Jun 27, 2018 at 8:38 AM Kenneth Knowles wrote: > I think it is just a matter of consensus. I have ope

Re: Jenkins emails

I think it is just a matter of consensus. I have opened https://github.com/apache/beam/pull/5784 to make it off, and then we can go through the individual job definitions to remove the parameter entirely. Two more reasons to remove this email config: - as job count scales up, email is just not s

Re: Jenkins emails

Thanks for the explanation, Kenn, I appreciate. Indeed my commits were on the website, so probably that's it. I presume not, but can I do something to facilitate the process? Best, Stefano ⁣Sent from Blue ​ On Jun 27, 2018, 17:23, at 17:23, Kenneth Knowles wrote: >First let me say what I thin

Re: Jenkins emails

First let me say what I think the cause is: - we have most jobs set to "email people who broke the build" - this scrapes what Jenkins thinks all the changes since last time are, and for every registered address, sends email - when we create a new job with these settings, *all* changes are consi

Jenkins emails

Hi all, I've contributed a couple of lines of code a couple of years back. Ever since a week, I started receiving email notification from Jenkins. How do I unsubscribe from those? I don't have an account on builds.apache.org. Best, Stefano