Re: Approach to build a cluster of Jenkins CI servers hands-off and tie them together?

To #7, slaves do not need the master config files at all, they only need the libraries used by the jobs. Our master has no executors, all jobs are built on slaves. Master and slaves have different config. Slaves running with user jenkins-slave (master jenkins), only the tools/libs are sync-ed, n

Re: Approach to build a cluster of Jenkins CI servers hands-off and tie them together?

On Tue, Oct 2, 2012 at 12:25 PM, zperry wrote: > Hi Les, > > Finally, the first sentence in "Distributed builds" wiki and the list from > Kohsuke Kawaguchi started making sense to me. Thank you once more for > sharing your experience. > > Regarding the list (shown below, and somewhat shortened an

Re: Approach to build a cluster of Jenkins CI servers hands-off and tie them together?

On Tue, Oct 2, 2012 at 11:16 AM, zperry wrote: >> >> I don't really see how that practice relates to a web service intended >> for both remote and local use from multiple users. The remote api does >> the same things as the regular http interface.It could work, of >> course, but it's not what

Re: Approach to build a cluster of Jenkins CI servers hands-off and tie them together?

Hi Les, Finally, the first sentence in "*Distributed builds*" wiki and the list from Kohsuke Kawaguchistarted making s

Re: Approach to build a cluster of Jenkins CI servers hands-off and tie them together?

Hi Les, [...] > > I don't really see how that practice relates to a web service intended > for both remote and local use from multiple users. The remote api does > the same things as the regular http interface.It could work, of > course, but it's not what people expect from a network servic

Re: Approach to build a cluster of Jenkins CI servers hands-off and tie them together?

On Mon, Oct 1, 2012 at 10:27 PM, zperry wrote: > > Reviewed the above, and saw this " When your Jenkins is secured, you can use > HTTP BASIC authentication to authenticate remote API requests. See > Authenticating scripted clients for more details." > > IMHO this is a piece of "ill-advice". With

Re: Approach to build a cluster of Jenkins CI servers hands-off and tie them together?

> This would be a starting point - there is also a cli and a way to use > groovy to access the whole api. > https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API > > Reviewed the above, and saw this " *When your Jenkins is secured, you can use HTTP BASIC authentication to authenticate

Re: Approach to build a cluster of Jenkins CI servers hands-off and tie them together?

Hi Les, Thanks for your follow-up. > > I have not found a reference in this regard, and would appreciate a > pointer. > > I will do the digging. > > This would be a starting point - there is also a cli and a way to use > groovy to access the whole api. > https://wiki.jenkins-ci.org/display/

Re: Approach to build a cluster of Jenkins CI servers hands-off and tie them together?

On Mon, Oct 1, 2012 at 4:22 PM, zperry wrote: > >> 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 appreci

Re: Approach to build a cluster of Jenkins CI servers hands-off and tie them together?

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

Re: Approach to build a cluster of Jenkins CI servers hands-off and tie them together?

On Sun, Sep 30, 2012 at 6:44 PM, zperry 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