You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by st...@baghino.me on 2018/06/27 15:10:46 UTC
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
Re: Jenkins emails
Posted by Mikhail Gryzykhin <mi...@google.com>.
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 <http://go/migryz-feedback>?
On Wed, Jun 27, 2018 at 9:42 AM Andrew Pilloud <ap...@google.com> wrote:
> 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 <kl...@google.com> wrote:
>
>> 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 sensible for managing their
>> status
>> - many/most changes are not relevant to the particular test being run
>>
>> Kenn
>>
>> On Wed, Jun 27, 2018 at 8:26 AM Stefano Baghino <st...@baghino.me>
>> wrote:
>>
>>> 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 <http://www.bluemail.me/r?b=13187>
>>> On Jun 27, 2018, at 17:23, Kenneth Knowles <kl...@google.com> wrote:
>>>>
>>>> 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
>>>> considered new, and jobs usually start broken, so everyone gets email until
>>>> the first passing run
>>>> - also we bulk merged the web site into the main repo, so *all*
>>>> website commits were also considered for all existing jobs
>>>>
>>>> We have had some other issues where Jenkins is emailing people with
>>>> *no* commits at all in any repo. Presumably due to an issue with looking up
>>>> registered users.
>>>>
>>>> I think we should just turn off "email people who broke the build". We
>>>> have other channels to monitor the status, and we don't need this spam or
>>>> administrative work.
>>>>
>>>> Kenn
>>>>
>>>> On Wed, Jun 27, 2018 at 8:10 AM < stefano@baghino.me> wrote:
>>>>
>>>>> 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
>>>>>
>>>>
Re: Jenkins emails
Posted by Andrew Pilloud <ap...@google.com>.
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 <kl...@google.com> wrote:
> 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 sensible for managing their
> status
> - many/most changes are not relevant to the particular test being run
>
> Kenn
>
> On Wed, Jun 27, 2018 at 8:26 AM Stefano Baghino <st...@baghino.me>
> wrote:
>
>> 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 <http://www.bluemail.me/r?b=13187>
>> On Jun 27, 2018, at 17:23, Kenneth Knowles <kl...@google.com> wrote:
>>>
>>> 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
>>> considered new, and jobs usually start broken, so everyone gets email until
>>> the first passing run
>>> - also we bulk merged the web site into the main repo, so *all* website
>>> commits were also considered for all existing jobs
>>>
>>> We have had some other issues where Jenkins is emailing people with *no*
>>> commits at all in any repo. Presumably due to an issue with looking up
>>> registered users.
>>>
>>> I think we should just turn off "email people who broke the build". We
>>> have other channels to monitor the status, and we don't need this spam or
>>> administrative work.
>>>
>>> Kenn
>>>
>>> On Wed, Jun 27, 2018 at 8:10 AM < stefano@baghino.me> wrote:
>>>
>>>> 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
>>>>
>>>
Re: Jenkins emails
Posted by Kenneth Knowles <kl...@google.com>.
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 sensible for managing their
status
- many/most changes are not relevant to the particular test being run
Kenn
On Wed, Jun 27, 2018 at 8:26 AM Stefano Baghino <st...@baghino.me> wrote:
> 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 <http://www.bluemail.me/r?b=13187>
> On Jun 27, 2018, at 17:23, Kenneth Knowles <kl...@google.com> wrote:
>>
>> 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
>> considered new, and jobs usually start broken, so everyone gets email until
>> the first passing run
>> - also we bulk merged the web site into the main repo, so *all* website
>> commits were also considered for all existing jobs
>>
>> We have had some other issues where Jenkins is emailing people with *no*
>> commits at all in any repo. Presumably due to an issue with looking up
>> registered users.
>>
>> I think we should just turn off "email people who broke the build". We
>> have other channels to monitor the status, and we don't need this spam or
>> administrative work.
>>
>> Kenn
>>
>> On Wed, Jun 27, 2018 at 8:10 AM < stefano@baghino.me> wrote:
>>
>>> 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
>>>
>>
Re: Jenkins emails
Posted by Stefano Baghino <st...@baghino.me>.
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 <kl...@google.com> wrote:
>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
>considered new, and jobs usually start broken, so everyone gets email
>until
>the first passing run
>- also we bulk merged the web site into the main repo, so *all* website
>commits were also considered for all existing jobs
>
>We have had some other issues where Jenkins is emailing people with
>*no*
>commits at all in any repo. Presumably due to an issue with looking up
>registered users.
>
>I think we should just turn off "email people who broke the build". We
>have
>other channels to monitor the status, and we don't need this spam or
>administrative work.
>
>Kenn
>
>On Wed, Jun 27, 2018 at 8:10 AM <st...@baghino.me> wrote:
>
>> 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
>>
Re: Jenkins emails
Posted by Kenneth Knowles <kl...@google.com>.
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
considered new, and jobs usually start broken, so everyone gets email until
the first passing run
- also we bulk merged the web site into the main repo, so *all* website
commits were also considered for all existing jobs
We have had some other issues where Jenkins is emailing people with *no*
commits at all in any repo. Presumably due to an issue with looking up
registered users.
I think we should just turn off "email people who broke the build". We have
other channels to monitor the status, and we don't need this spam or
administrative work.
Kenn
On Wed, Jun 27, 2018 at 8:10 AM <st...@baghino.me> wrote:
> 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
>