On Thu, Jul 26, 2012 at 9:06 AM, Lukas Rytz <lukas.r...@epfl.ch> wrote:
> There was a delay of ~10 seconds between starting each build.
>
> You can see some details in the screenshot of my original post: We have 5
> slaves here,
> one of them was already running one job, all of the others were idle.
>
> It would be nice if the scheduling was configurable. It seems that the
> "Throttle Concurrent
> Builds" plugin [1] works in that direction: it can make sure to never run
> more than X builds
> on one machine. What I'm looking for is not a limited, but a balanced
> scheduling.
The simple-minded strategy is that if you don't want 6 jobs running on
a single machine, don't start 6 executors there - and if running 6
concurrent jobs is OK, just let it go. When you have a larger set of
jobs, randomness will eventually take over. But, I agree that it
would be nice if jenkins would favor the least-loaded machine when
starting a new job that had not been run before and thus does not have
an established location preference. You could disconnect the machine
that has assumed too much of the load and run a few jobs to force them
to migrate.
--
Les Mikesell
lesmikes...@gmail.com
