Thanks a lot for your answer. I found your previously posted solution to this here: https://groups.google.com/d/msg/jenkinsci-users/2NfS9IEw52o/QPC6E88gWTcJ
- David On Saturday, September 14, 2013 1:07:36 AM UTC+3, slide wrote: > > You could always send it along as parameters. You could use a groovy > template and look back through the job causes and grab the committers at > each level (I've posted on how to do this on the mailing list before). I'm > sure there are other ways you can do it two, but those are the ones that > pop into my head right now. > > > On Fri, Sep 13, 2013 at 1:21 PM, David Resnick <[email protected]<javascript:> > > wrote: > >> I have a chain of 3 jobs, A->B->C. >> >> Job A is triggered by SCM polling and job C uses the email-ext plugin to >> send emails to committers. >> >> My problem is that job B checks out some build script related code from a >> separate SCM, overridding the committers from job A. I don't mind having >> the job B committers (there usually aren't any) getting emails for failed >> job C builds, but I do need to have job A committers getting emails too. >> >> How can I set this up? What approach could I use to have the job A >> committers/culprits added to the recipients of emails sent by job C? >> >> Thanks, >> David >> >> -- >> 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 [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
