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? --Rob The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle & Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle & Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
