You can use the Multi slave config plugin to manage you slaves easier: https://wiki.jenkins-ci.org/display/JENKINS/Multi+Slave+Config+Plugin The platform labeler plugin is also handy if you have a heterogeneous cluster https://wiki.jenkins-ci.org/display/JENKINS/PlatformLabeler+Plugin
We use those plus a bunch of bash scripts to manage hundreds of slaves. /B On Tuesday, June 5, 2012 9:47:01 AM UTC+2, Dirk Kuypers wrote: > > Hi, > > or, just another suggestion: Use groovy to programmatically change or > even create the jobs. I am just starting to use it to create dozens of > unit test jobs and I am really impressed about the power although it > is quite hard in the beginning to read through Jenkins API. > > Some links to start with: > https://wiki.jenkins-ci.org/display/JENKINS/Groovy+plugin > https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin > http://scriptlerweb.appspot.com/catalog/list > > Another option I used before was some unix command lline acrobatics > with find and sed to change specific config.xml files. After doing > that you have to restart Jenkins or just "Reload configuration from > disk". > > HTH > Dirk > > 2012/6/5 Les Mikesell <lesmikes...@gmail.com>: > > On Mon, Jun 4, 2012 at 5:35 PM, phil swenson <phil.swen...@gmail.com> > wrote: > >> if i want to make a change to every job, I have to do it 50 times. > >> > >> if i want to make a change to every node, I have to do it 20 times > > > > OK, but those things go away when you get it right and stop making > > configuration changes. Normally the things you change should be under > > source control as part of the project that jenkins checks out. Or, if > > your jobs really are that variable, maybe you can use a parametrized > > build where you pass int the changing parts. > > > > -- > Never trust a short-haired guru >
