Released 2.38.1 today, should fix this issue.
On Mon, Jun 2, 2014 at 12:27 PM, Slide <slide.o....@gmail.com> wrote: > That's a valid point. I do actually have an easy fix for this, I'll > release as soon as I can. > > > On Mon, Jun 2, 2014 at 10:10 AM, Daniel Beck <m...@beckweb.net> wrote: > >> >> On 02.06.2014, at 14:05, Slide <slide.o....@gmail.com> wrote: >> >> > I don't think its valid to not have at least one type of recipients >> selected. >> >> I use that a lot. The problem is that the per-trigger list of recipients >> is not part of this mechanism. >> >> Example: >> >> In case of success, send email to a...@example.org (Success trigger, >> Advanced, Recipient List). >> In case of failure, send email to b...@example.org (Failure trigger, >> Advanced, Recipient List). >> >> - No Project Recipient List (although it'd be a workaround for this >> problem to leave that field empty and select 'Recipient List' anyway) >> - No Culprits >> - No Developers >> - No Requestor >> >> Configure your notification like this, and Jenkins goes *boom* >> >> -- >> 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-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Website: http://earl-of-code.com > -- Website: http://earl-of-code.com -- 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
