However, since our most recent upgrade, on success an email is sent to the global recipient list. It looks like this is a bug introduced in version 2.15 of the plugin, possibly associated with the fix for https://issues.jenkins-ci.org/browse/JENKINS-10783. Or it might have started happening when we last upgraded Jenkins.
Has anyone else seen this?
Thanks
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
On 14/09/2011 12:12, Matthew...@Diamond.ac.uk wrote:
> We use the email-ext plugin, and have configured a "Success" trigger" which, in the "Advanced" section, has all "Send to ..." options DE-selected. Thus if a build succeeds (and the previous build was also a success), then I don't expect any email to be sent.
>
> However, since our most recent upgrade, on success an email is sent to the global recipient list. It looks like this is a bug introduced in version 2.15 of the plugin, possibly associated with the fix for https://issues.jenkins-ci.org/browse/JENKINS-10783. Or it might have started happening when we last upgraded Jenkins.
>
> Has anyone else seen this?
I thought that the "Success" trigger always emails. I think that you are
wanting to use the "Fixed" trigger. The latter only sends on the first
success after a group of failures.
Regards
Richard
Try removing PROJECT_DEFAULT_RECIPIENTS from the trigger's list of recipients.
Removing PROJECT_DEFAULT_RECIPIENTS solved the problem. Thanks.
No, I only removed them from the “Success” trigger – the one that I had defined, but had all "Send to ..." options DE-selected.
I think the email-ext plugin is confused about recipient lists. There is a system-wide recipient list defined under “Manage Jenkins”, then in each job which uses email-ext there is a “Global Recipient List” (which is not system-wide as the name global might suggest), and then for each separate trigger there is a “recipient” list. It is not at all clear how these interact, and what the “send to recipient list” really means.
Hope that helps.
Matthew
I have seen this behaviour since upgrading to Jenkins 1.430 and email-ext plugin 2.15. Unfortunately, I can’t find a way of downgrading the plugin to 2.14.1.
David
Click here to report this email as spam.
Having removed $PROJECT_DEFAULT_RECIPIENTS from the job config, I now find that it has mysteriously re-appeared! Presumably because I restarted Jenkins. It looks like this was broken in 2.15.
I have opened ticket https://issues.jenkins-ci.org/browse/JENKINS-11061 for this.
I'll take a look
Slide
Matthew...@Diamond.ac.uk wrote:
>On Thu, Sep 15, 2011 at 3:57 AM, <Matthew...@diamond.ac.uk<mailto:Matthew...@diamond.ac.uk>> wrote:
>Removing PROJECT_DEFAULT_RECIPIENTS solved the problem. Thanks.
>
>From: jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com> [mailto:jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com>] On Behalf Of Slide
>Sent: 14 September 2011 12:51
>To: jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com>
>Subject: Re: Email-ext sends an email when it shouldn't
>
>
>Try removing PROJECT_DEFAULT_RECIPIENTS from the trigger's list of recipients.