The attached Jenkinsfile's "tools" block does not add the JDK's path to the PATH variable as expected.

Workarounds:

• Moving the "agent {label 'abc && def'}" line up to replace the top-level "agent none" results in the path to the JVM being set properly.
• Moving the "tools" block up to line 6 so that it is at the same level as the "agent {label 'abc && def'}" clause also results in the path to the JVM being set properly.

Please consider improving the usability here. It seems like if Jenkins is unable to honor a "tools" block that it shouldn't silently proceed. If it had printed an error stating that the tools block has to be associated to a new node allocation this would have been a quick problem to resolve.