I'm not sure if that is possible given that the first job has already finished prior to the various artifacts being generated.
I guess the question is what you want to do with those artifacts in the first build (that is, why are they important to bubble up there rather than drop down to the package step)? (As an aside, also just wondering why the build doesn't kick off at the build step directly and set the version number in there?) Cheers Richard. On Wed, Aug 1, 2012 at 8:48 AM, Glenn MacGregor <glenn...@gmail.com> wrote: > Hi All, > > I have a build which has 4 Jenkins jobs, the first just downloads the source > from svn and sets a version number. The second is the build step, third is > the unit test step and the fourth is the package step. Each is kicked off > using the parameterized trigger plugin and that is working great. I would > like to have all the artifacts bubbled up to the first job which is the one > I kick off. > > I have been looking through the plugins and mailing list but have not found > any solutions for this. Does anyone have any ideas on how to make this > happen? > > Thanks > > Glenn
