Jenkins Email Notifications

[Christian Flamm]

Hi,
I have a problem understanding Jenkins' email notification configuration. There are three things I can set

1. List of additional Recipients
2. Yes/No - Send e-mail for every unstable build
3. Yes/No - Send separate e-mails to individuals who broke the build

I just cannot seem to configure: Only send an email to the committer(s) of the first failing build. No emails should be sent to any committers for any consecutively failing build after this one.

My naive assumption was to enable this by setting 2. = No and 3. = Yes. But weirdly his will (a) send emails for every failing build and (b) to every committer since the build failed for the first time.

Anyone?

Thanks in advance,

Christian

[Jacek.Tomaka]

Hi Christian,

We wanted to configure this plugin In the same way as you wanted but it does not seem possible.

I guess the rationale here is that :

1. When build is broken it should be a priority for the team to fix it.

2. All the checkins after the one that broke the build might or might not cause the build to fail, even after the problem that caused the build to fail is fixed. There's no way Jenkins can tell.

What is your use case here?

Regards.

Jacek Tomaka

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c140aa48-8e9d-473c-9d1c-ae451e7f5cdd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Christian Flamm]

Hi Jacek,

I absolutely agree with the two points you brought up. Having Jenkins notification behavior like this is IMHO a very reasonable standard setting for many situations. I just wonder why I can't seem to configure the behavior to whatsoever I believe is necessary. I mean.. there are check boxes to check/uncheck.. what are they for?

My use case: We have many, many branches and corresponding CI jobs (on-push) for each of them. On some of these branches only 1 or 2 people work. The main reason I believe it's necessary to implement my desired behavior for some branches is: Jenkins must never spam!

1. Don't spam the right people: On relatively "unimportant" branches, the person who broke the build first is exactly the right person to notify. Don't tell him over and over again - he knows and he's working on it according to his work priorities. 
2. Don't spam the wrong people: After a branch build breaks the team working on it might integrate the master branch progress (via git merge). All the authors that committed stuff on the master branch are now authors of that branch, too. Don't send them mails, it's not their fault, they don't know, mostly they don't care.
   

After three years of experience with Jenkins using the standard notification setting

1. people often receive redundant notifications which they find unnerving (=spam)
   
2. people often receive confusing notifications about branches they don't even know about and about which they don't care (=spam)
   

If I want people to take such notifications seriously I must send as little of them as possible. Else people will perceive them as noise. That's the last thing I want.

Regards, Christian

[Slide]

You could check out the email-ext plugin. I has a lot of configurability.

--

You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/83fd1216-241b-4c95-ac14-c1c1c4d50561%40googlegroups.com.

[Christian Flamm]

Hi, thx, did that already.

What I liked was how easy it is to send an email to the person responsible for the first build break in an row. That works great.

What I didn't like was how well it worked to send a "back to stable" email to that person again. It seemed to have trouble determining the "suspects" it had sent the "you broke the build" email in the first place.

I guess I'll switch to email-ext anyway. But I found it really confusing why the standard mailing has two check boxes that seem to be exactly what I believe I need. But they don't seem to have any effect.

Would be great if someone spots my lack of understanding those check boxes :-)

[Christian Flamm]

Hey slide - after seeing some postings of yours I'm under the impressionism you might have something to do with email-ext...? :-)

Having a look at my initial posting - how would you configure emai-ext to achieve the desired behavior?

Regards + thanks in advance,
Christian