Hi Sebastian,
the 'parent' matrix builds are always fly-weight tasks. So you do not
need to configure that explicitly. Only the individual 'child' matrix
runs spawn by the matrix build (in your example: C1, C2, C2, ...) will
take up an executor.
By the way: matrix runs are executed in parallel by default. You would
have to check the "Run each configuration sequentially" option
explicitly to switch that off.
Do you experience any specific problem with your current setup?
Cheers,
Simon.
--
Sebastian Sawicki (18.06.2012 02:11):
Hi,
I've got one build scenario (Scenario) which can be run by several
configurations:
Scenario(Configuration c) where c=C1, C2, C3,...
The matrix build would fit here, cause I can set the configuration axes
to cover each Configuration.
However, what I need is to build some subset of those configurations in
a few different matrixes i.e.:
M1: C1, C2, C3.
M2: C1, C3.
M3: C2, C3.
Therefore I thought about setting the Scenario as a parametrized job
(where the current configuration will be set in the parameters) with the
option set to enable concurrent builds. And then to launch this job with
the given parameters from the matrix child build.
As I understand this approach will consume 2 executors for each running
configuration build (one for the matrix and second for the actual
Scenario) although the matrix build will not do anything but waiting for
the Scenario to complete and then just archive its artifacts.
So here comes my question: If there is a possibility to set this whole
matrix to act as flyweight task (and not to consume any
jenkins-configured executor), since the job is done only by the Scenario
and the matrix is intended just to choose which configurations would run?
