Les, Thanks for your comments.
> It is probably pretty rare to need more than one or a few masters, and > if you do it would be because they had to be configured differently. > In the near term, we only need one master. > > I've never needed enough slaves that it was a problem to click the > 'copy existing node' button and click 'OK', *but maybe there is a way > to do it through the rest interface. * I have not found a reference in this regard, and would appreciate a pointer. I will do the digging. > For linux slaves started via ssh you don't really need anything for > jenkins other than the jvm and a > suitable user account. All these have been done. Right now, for POC, I have setup three KVM guests (all done via kickstart hands-off): - Ubuntu 12.04 64bit - Ubuntu 11.04 64bit - Fedora 17 64bit All have openjdk, Jenkins packages installed, all can ssh to each other as the 'jenkins' user. The main use is to check our C++ builds, together with running tests written in bash and Python. The master and the two slaves are to run the same upstream/downstream jobs. > The larger problem is making sure the slaves have all of the (very > arbitrary) build tools available that some > user's job might invoke. > Not a problem for us. All GNU tools and others (e.g. md5deep, tree) are installed during the server configuration phase. Done already. All we need is just enough info so that we can tie these CI hosts together programmatically. Results from mouse clicks are not easily reproducible, but Results from running scripts + templates are, and can be even idempotent. That's what we would like to accomplish. > -- > Les Mikesell > lesmi...@gmail.com <javascript:> > Regards, -- Zack
