If you can get to the failure reason from code, using the groovy template feature of email-ext might work for you
Sent from my Windows Phone ------------------------------ From: Joern Boegeholz Sent: 2/25/2013 6:04 To: jenkinsci-users@googlegroups.com Subject: Email-Notification with build failure reason in a poll / build scenario To decouple syncing from the rcs and building multiple variants of our project we use "trigger/call builds on other projects" as build trigger in a "poll" job. The poll job syncs and triggers multiple build jobs (e.g. release / debug version) It fails when one build job fails. This approach minimizes RCS traffic and email notification. The downside of this approach is that the poll job doesn't know why a build job failed. The email which is sent out just states "build failed" and the last rcs changes. We need to put the root cause of the build failure.into this email. Any ideas? Best Regards Joern -- 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/groups/opt_out. -- 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/groups/opt_out.
