On Sun, Sep 30, 2012 at 6:44 PM, zperry <zack.pe...@sbcglobal.net> wrote:
>
> Our environment is a strictly Linux environment (CentOS, Scientific Linux,
> Fedora, and Ubuntu). Both of us are competent in setting up large clusters.
> We typically use tools like cobbler + a configuration management tool
> (Puppet, Chef, and alike) to set up a large number of machines (physical
> and/or virtual) hands off (hundreds of nodes in less than an hour typical).
> We would like to do the same for nodes running Jenkins. But the step by step
> guide doesn't give us any clues in this regard.
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.
> Personally I don't mind configure the master via the Web UI (although I
> would love to automate this part if I have the necessary info). But being
> used to dealing with hundreds or more machines hands-off, clicking the UI
> for many machines just doesn't feel right. Can someone point to us a
> documentation that talks about how to set up large cluster of Jenkins CI
> hosts more in the hands-off way?
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. For linux slaves started via ssh
you don't really need anything for jenkins other than the jvm and a
suitable user account. The larger problem is making sure the slaves
have all of the (very arbitrary) build tools available that some
user's job might invoke.
--
Les Mikesell
lesmikes...@gmail.com
