Yes, having multiple slaves per machine would give even more flexibility,
which'd be nice to have.
I use the EC2 plugin to spawn slaves, however, and it looks like it doesn't
support having multiple slaves per instance.
--
You received this message because you are subscribed to the Google Grou
Hi
You could add a slave with one executor on each of the physical servers that
handle only the restricted builds.
//stefan
> 4 mar 2016 kl. 22:09 skrev Tom Fitzhenry :
>
> A less-than-ideal-but-possibly-okay solution is:
> 1. Set one of the build slaves to 'Only build jobs with label restrict
A less-than-ideal-but-possibly-okay solution is:
1. Set one of the build slaves to 'Only build jobs with label restrictions
matching this node', set the label to "parallelisable", and set the number
of executors to 5.
2. Label all parallelisable jobs as "parallelisable"
The problem with this is
I have 3 build slaves and ~100 jobs:.
* about ~80 jobs (it varies day-to-day), that require exclusive access to
the file system, and hence cannot be run at the same time, on the same node.
* about 20 jobs, that do not use the filesystem, and can be run in parallel
Since most jobs require exclusiv
