Question

We use Jenkins for our CI build system. We also use ‘concurrent builds’ so that Jenkins will build each change independently. This means we often have 5 or 6 builds of the same job running simultaneously. To accommodate this, we have 4 slaves each with 12 executors.

The problem is that Jenkins doesn’t really ‘load balance’ among its slaves. It tries to build a job on the same slave that it previously built on (presumably to reduce the time syncing from source control). This is a problem because Jenkins will build all 6 instances of our build on the same slave (or more likely between 2 slaves). One build machine gets bogged down and runs very slowly while the rest of them sit idle.

How do I configure the load balancing behavior of Jenkins, and how it controls its slaves?

Answer 1

If you do not find a plugin that does it automatically, here’s an idea of what you can do:

• Install Node Label Parameter plugin

• Add SLAVE parameter to your jobs

• Restrict jobs to run on ${SLAVE}

• Add a trigger job that will do the following:

  • Analyze load distribution via a System Groovy Script and decide on which node to start next build.
  • Dispatch the build on that node with Parameterized Trigger
    plugin
    by assigning appropriate value to SLAVE parameter.

In order to analyze load distribution you need to install Groovy plugin and familiarize yourself with Jenkins Main Module API. Here are some useful initial pointers.