Hi, I think this plugin can help https://wiki.jenkins-ci.org/display/JENKINS/Job+Import+Plugin to list what's available on the other instance to be launched
I can also provide some Java code to do remote job launching with authentication when needed. Just let me know By combining the 2, you should be close to achieve what you want regards didier On Mar 2, 5:52 pm, Jim McCaskey <jim.mccas...@pervasive.com> wrote: > Aaron, > > Thanks for the feedback. I was afraid it would boil down to something like > that. I was hoping for a solution which a novice could use pretty easily. > One of the great things of administering Jenkins is that it's pretty easy to > set up and get going. I looked for a plugin you suggested but couldn't find > it. Even if it was too restrictive I could try and find some time to augment > it to do what I want. I suppose I could always start from scratch. :) > > -Jim > > > > > > > > -----Original Message----- > From: jenkinsci-users@googlegroups.com > [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Neerenberg, Aaron > Sent: Friday, March 02, 2012 10:22 AM > To: jenkinsci-users@googlegroups.com > Subject: RE: Handing off builds between Jenkins masters > > Jim- > > I remember there being a plugin, a while back, which would allow one Jenkins > instance to invoke jobs directly upon another; however, it required that the > job be defined on both servers with the same name. I currently run several > Jenkins instances (different dev centers), and, for the most part, ended up > just using a group of wget calls to call the correct URL's for the API of the > target instance. > > Regards, > Aaron > > -----Original Message----- > From: jenkinsci-users@googlegroups.com > [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jim McCaskey > Sent: Friday, March 02, 2012 7:52 AM > To: 'jenkinsci-users@googlegroups.com' > Subject: Handing off builds between Jenkins masters > > 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
