I wouldn't call that behavior "normal". I'm new to Jenkins pipelines and Groovy scripting, and this has been the single most maddening thing to overcome in my attempts to learn the environment. On what planet does it make sense that enclosing something in a node block, where the only argument is a node label, and where the block is enclosed in {} braces (which defines an isolated "scope" in every other language I can think of) does not cause the label to become used as the default for everything defined therein? The backflips you have to go through to overcome this are ridiculous. I find both the "node" and "agent" constructs as implemented by the Jenkins pipeline mechanism to be completely useless.
On Wednesday, December 14, 2016 at 6:42:09 AM UTC-6, mpapo - Michael Pailloncy wrote: > > IIUC, it's a normal behaviour. > > The "build" pipeline step triggers the job job1 without any node "context" > (a bit like if you trigger it manually), so the default label of job1 is > used in this case. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2424b270-68d1-48b7-aac1-4a8298a36c89%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.