- 
    Bug 
- 
    Resolution: Not A Defect
- 
    Minor 
- 
    Jenkins 2.11
 Pipeline plugin 2.2
I have a Jenkins pipeline job called "TestPipeline". I want to trigger a build on 2 different slaves which labeled "tester1' and "tester2". And the pipeline script is quite simple here:
node('tester1') { build 'test_job' } node('tester2') { build 'test_job' }
However when I run the TestPipeline job, the "test_job" won't run on the nodes which I assigned. But run on random nodes instead.
I'm wondering if I should set "Restrict where this project can be run" on my "test_job". So I set it to "tester" (The "tester" label contains both node "tester1" and "tester2"). But when I run the pipeline job again, the "test_job" runs on "tester2" twice. I should expect the job to run on "tester1" first and then run on "tester2".
So the build job step runs regardless of node step?
- is duplicated by
- 
                    JENKINS-43003 label parameter does not enforse execution on the labels -         
- Closed
 
-         
- is related to
- 
                    JENKINS-39365 Can't restrict a pipeline job to agents to run on -         
- Resolved
 
-