I am facing the same issue. I made some initialization jobs for slave nodes, which run when the slave starts. A Matrix job forces the installation of multiple JDKs and multiple Maven versions. After that it performs some testing to verify the proper installation of the tools. This Matrix job is triggered by another job that specifies the parameter build on same node for the Matrix job.

Possible solutions:

• All Matrix sub-jobs should inherit this setting by default. This setting can be overridden by choosing a value from the Slaves axis or label expression axis.
• Maybe it is an idea to define also a virtual label same node in the Slaves axis or label expression axis.

NodeLabel Parameter allows to restrict jobs in a such way

I do agree that there are at least two solutions for this problem

• NodeLabel parameter plugin with only one option/slave to be chosen
• add slave axis with only one slave
  but both add additional complexity for maintaining the matrix job. The advanced option "Restrict where this project can be run" should IMHO do exactly this.

I agree that "Restrict where this project can be run" should be inherited by matrix jobs by default. It surprised me when it didn't work.

A nice to have would be to be able to configure it per axis or per particular job. I can see how the job would override the axis, that would in turn override the main job value.

I have a problem using the following situation.

I use a jenkins master and some virtual machines as slaves to start parallel tests.
The virtual machines are configured to use a special test environment (database, WAS, JDK) in every vm.
The test uses a matrix configuration to manage the different test configuration.

At the start of the test every slave VM is resetted to a defined snapshot, to make sure the test conditions are always equal.
After booting the VM, the build, selected for testing is installed on the jenkins slave VMs.
If the Matrix jobs are started on a slave, the testresult is always failure due to the reset to the snapshot of the slave VM and the resultng network error.
So I need the possibility to make sure, all the matrix jobs are started on jenkins master.

Hello,
I think I solved my problem.
I tried to restriced at first the execution of the matrix jobs bei a label expression in the advanced project settings.
But that does not work.
Now I use a simple groovy script to restrict the job to the master.
The script is

<pre>
return "Master";
</pre>

Now all the matrix childs are executed on the jenkins master as I need in my test environment.

Hello @Reiner Writz

Where have you put your script to force execution in the master ?

Thanks

Hello @Reiner Writz

Where have you put your script to force execution in the master ?

Thanks

In the first section of the multiconfiguration is an option to enter a groovy script to restrict where the job could be run.
Activating this option opens an edit field for the groovy script.
In this field I entered the mini groovy script: return "Master";
This worked fine.