I appreciate it's not a bug, which is why I wrote 'bug' in quotes :-) I've looked at the suggestion and, although I can roughly understand what it's doing, I know nothing about Groovy or the Jenkins object model at the moment so it may take me a while to work out how to fill in the blanks; perhaps Christian will have updated his changes by then and I'll just need to select a checkbox ;-)
Thanks again John On Friday, 13 June 2014 13:21:44 UTC+1, slide wrote: > > It's actually not a bug, you CAN indeed pick up committers from upstream > (I even showed how to do it using a script). I use it now in my setup at > work. > > slide > > > On Fri, Jun 13, 2014 at 5:16 AM, John McCabe <[email protected] > <javascript:>> wrote: > >> Thanks for your reply. I'm fairly new to Jenkins so will have to look >> further into the fingerprints stuff you mentioned. >> >> I've just had a look at the email-ext plugin page and found there's a >> 'bug' listed relating to picking up committers from upstream jobs! >> https://issues.jenkins-ci.org/browse/JENKINS-17742. I'll keep an eye on >> that and see if it says anything useful. >> >> Thanks for pointing me in that direction! >> John >> >> >> On Friday, 13 June 2014 12:49:49 UTC+1, slide wrote: >> >>> You can do all those things with email-ext, but unless you are using >>> fingerprints to have dependencies between the builds, the Mailer plugin >>> will not send to the people from upstream builds. >>> >>> slide >>> >>> >>> On Fri, Jun 13, 2014 at 4:39 AM, John McCabe <[email protected]> >>> wrote: >>> >>>> I've got a chain of 'builds' as follows: >>>> >>>> CVS Checkout >>>> Compile for target X >>>> Static Analysis >>>> Compile for target Y >>>> >>>> I have them all set up to notify people who broke the build using >>>> email. Am I right in thinking that the source control differences are used >>>> to work out who to email in those cases? The only 'build' I have that >>>> shows >>>> those differences is the CVS checkout one so am I right in assuming that, >>>> in those cases, the concept of notifying these people will fail? >>>> >>>> If so, is there any way, given this chain, that a failed build can get >>>> the change details from a 'build' earlier in the chain in order to send >>>> those notifications to the right people? >>>> >>>> Thanks for any suggestions >>>> John >>>> >>>> -- >>>> 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/d/optout. >>>> >>> >>> >>> >>> -- >>> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > 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/d/optout.
