That sounds like an issue in the email-ext. I get mails from the normal jenkins mailer.
/James From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Tim Jackson Sent: 30 April 2014 23:05 To: jenkinsci-users@googlegroups.com Subject: Re: New build flow seems to break many things I agree that .11 is a huge step backwards for me. As far as I can tell, the build flow plugin no longer triggers the failure event of the email-ext plugin. So I am no longer getting failure mails for the overall job. Setting up a new job to handle the failure mail is redundant and can fail itself, thus changing the results. I am more apt to just dump the build flow plugin and find a more suitable method. It is very disappointing to have functionality removed. A lot of us have based large amounts of work on what it did. - Tim On Friday, April 18, 2014 10:13:26 AM UTC-6, Greg Dickie wrote: Hi, We updated to the latest build flow without workspaces and all of the change reporting seems to have broken. In addition builds are no longer finding the latest git commit on branches. This is quite a setback for us. What was the rational for those changes and is there an alternative mechanism in the new plugin to get this functionality back? Thanks, Greg -- 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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>. For more options, visit https://groups.google.com/d/optout. -- 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.