Hi Chris, Sorry, no joy so far. It's been a while since I tried to fix it. I'll try to take a look at it again. Can't promise a time frame though.
Regards, Fred On Friday, January 25, 2013 10:53:11 AM UTC+1, Chris Withers wrote: > > Hi Fred, > > Did you have any joy with this? > > I've using 1.25 but can't see anything that would let me specify the > triggering project in the "Project name" box. I'd imagine it would be > some kind of place holder variable such as $COPYARTIFACT_UPSTREAM_JOB or > some such? > > cheers, > > Chris > > -------- Original Message -------- > Subject: Re: copy artifacts - pick from two upstream jobs > Date: Fri, 24 Feb 2012 18:54:10 +0000 > From: Chris Withers <ch...@simplistix.co.uk <javascript:>> > To: jenkins...@googlegroups.com <javascript:> > CC: Fred G <fred...@googlemail.com <javascript:>> > > Hi Fred, > > On 21/02/2012 15:23, Fred G wrote: > > You can use the "Upstream build that triggered this job"-functionality > > of the Copy-Artifacts-Plugin. > > Unfortunately you still need to specify the name of the triggering job. > > I will try to fix this in an upcoming version. > > That would be great :-) > > > Until then you need to specify two "Copy artifacts from another project" > > build steps (one for each triggering project) and mark them as optional. > > This works just fine! > > thanks, > > Chris > > -- > Simplistix - Content Management, Batch Processing & Python Consulting > - http://www.simplistix.co.uk > > > --
