We are wanting a similar thing. We want a successful build to kick of a particular parameterized build on another master. Right now, we've prototyped using wget (using "buildWithParameters") from within the flexible publish plugin so that it can be a post-build action. It seems to work fine, but it really feels like a cludge. If anyone does end up writing some plugin code for this, I would be happy to test it.
On Sat, Mar 3, 2012 at 11:20 AM, Sami Tikka <[email protected]> wrote: > I have recently used the ssh API because it allows one to trigger a build > and wait for its completion, which was useful for one seldom-used task. > > -- Sami > > danny staple <[email protected]> kirjoitti 3.3.2012 kello 11.50: > > We've used the wget/curl methods quite successfully for this. It's worth > getting to know as it also allows builds to start other builds in ways the > plugins dont usually cover - although we are taking note of the ssh API. > > On 3 March 2012 07:33, domi <[email protected]> wrote: >> >> We do this with wget in a shell step >> >> $> wget http://someserver.com/job/jobA/build?delay=0sec >> >> …just the same way as if you would trigger it from a command line. >> If you use the conditional-buildstep-plugin you can wrap the execution >> into conditions too. >> /Domi >> >> >> On 02.03.2012, at 16:52, Jim McCaskey wrote: >> >> > Hello all, >> > >> > I've looked around for a bit for something to do what I want, and before >> > I spend a whole lot of time hacking around, I thought I would ask. I would >> > like to be able to have one Jenkins master start a build on another Jenkins >> > master. Just like the existing "Build other projects" functionality, but >> > instead of calling the other project on the local Jenkins Master, call it >> > on >> > a remote Jenkins master. >> > >> > Why do I want to do this? Our Jenkins use is growing internally (a good >> > thing!) and other groups want to use the system for their own automation >> > purposes. These other groups are doing more detailed testing, integration >> > work, and some system maintenance and the existing Jenkins administrators >> > don't want to deal with that. There's also the issue of passwords/security >> > to deal with between the completely separate groups. It seems like if >> > there >> > was a way to spawn projects off on another Jenkins master than the other >> > groups could have their own masters and work them as they see fit. >> > >> > I've thought of a few ways to handle this (the Jenkins CLI immediately >> > comes to mind), but wanted to know if there was a cleaner implementation >> > that could make this happen. >> > >> > Thanks! >> > >> > -Jim >> > >> > > > > -- > Danny Staple > > Director, ODM Solutions Ltd > w: http://www.odmsolutions.co.uk > Blog: http://orionrobots.co.uk/blog1-Danny-Staple > >
