Hi Chris, On 17.05.2013, at 19:29, Chris Withers <[email protected]> wrote:
> I've given up on the Throttle Concurrent Jobs plugin, it's buggy, and doesn't > work. We've fallen back to having a bunch of slaves with database servers on > them that only have one executor. They're tagged up with db server version > and os version and we use those as axes in the matrix. It works fine, but it > means that other builds (C++ compiles, python and JS static code analysis, > etc) can't run on those hosts, which is a shame as they're quite beefy hosts > with plenty of spare cycles... You can run several slaves on the same host. I've been using this approach to prevent parallel execution of specific jobs for about two years. One slave node is labeled with the required resource (e.g. 'database') and has one executor, the other has no relevant label and has four executors. Run the jobs that don't need exclusive access to the resource on the second node. Both nodes have their own home directory, and might run as the same or a different user. I've used this approach on Windows (some SCM tool didn't allow parallel checkout/update) and Linux (homebrew build scripts with hard-coded paths for temporary files). Regards Daniel -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
