Haev a look at the Multi-Job plugin. This is essentially what we do as well, and use the Multi-Job plugin Job as the Master .
... Mgimza On Wed, Dec 19, 2012 at 2:28 PM, Ken Beal <kenbealimpriv...@gmail.com>wrote: > Hi,****** > > ** ** > > I have three jobs. A invokes B, waits for it to complete, and then > invokes C. B gets some data dynamically. This needs to be given to C.*** > * > > ** ** > > (The real names for these jobs are "Monitor", "Deploy", and "Test"; we're > building a deployment pipeline, post-build.)**** > > ** ** > > Job B gets some new data, in our case an IP address. This needs to be > sent to C so that it can perform its tests on the right deployment.**** > > ** ** > > ** ** > > One way to do this is using the Parameterized Trigger Plugin, defining A > to invoke B, and B to invoke C. However, we want to configure it > conceptually with a "master" job invoking each downstream job, so that e.g. > one could invoke B by itself, without it requiring running C after it runs > (e.g., for debugging purposes).**** > > ** ** > > We currently have a workaround where A creates a unique network folder, > passing that as a parameter to B and C; when B completes, it writes the IP > address to a file at the network location, and then when C starts, it reads > that file from there.**** > > ** ** > > However, I'd prefer to not depend on an external network resource if I can > help it. Is there a method to have B return data to A which can then be > passed to C as normal Jenkins parameters?**** > > ** ** > Thanks, > Ken > >
