This only works if there is fingerprinting being done between the two jobs. If you are using the email-ext plugin, you can pretty easily do this with the $SCRIPT content tag inside the recipients box and then have it execute a groovy script to look at the upstream causes. There is info on how to do this on the mailing list archives.
slide On Wed, Jul 18, 2012 at 3:01 PM, Sami Tikka <sjti...@gmail.com> wrote: > At least in the past it was possible to enable Jenkins to carry this > information to downstream jobs by setting a system property > hudson.upstreamCulprits to true. > > More information at > https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties > > -- Sami > > Varghese Renny kirjoitti 18.7.2012 kello 15.41: > >> >> I have job A which will trigger build based on polling scm. This build will >> trigger another job B. After this job B success, i have to send email >> notification to those who commit code on job A. >> How can i send email notification for the commiter of job A ? >> >> >> >> >> >> Thanks in Advance, >> varghese > -- Website: http://earl-of-code.com
