On Wed, Mar 28, 2012 at 1:26 PM, Mandeville, Rob <[email protected]> wrote:
> I’m running a build farm with about 60 active branches at a given time. The
> machines on our build farm can comfortably run 5-8 build and test jobs at
> any given time, with one stipulation: each build and test job needs to be in
> its own Unix account. Getting around that is more trouble than it’s worth.
>
>
>
> Currently, we’ve been handling that by giving each build account on each
> build machine its own one-executor slave. However, Jenkins appears to work
> under the assumption of one slave per host. I could do that by running the
> slave as on an account that can sudo to all the build accounts, and having
> one executor per build account. The build steps would all have to be run
> inside sudo commands.
>
>
>
> Has anybody ever dealt with this problem, and is it worth it to go to the
> one slave per host model?
The easiest solution is probably to run several virtual machines per
physical server since that makes everything cookie-cutter simple.
But, I don't think anything really ties the jenkins node to a unique
host. You should be able to add nodes that are configured to be
started by ssh with the same target address but a different user in
the connection options as long as you set up appropriate keys.
--
Les Mikesell
[email protected]
