[JIRA] (JENKINS-54646) External jars in shared libraries are always executed on master

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title

Andrew Bayer resolved as Not A Defect   Yes, this is as designed - Pipeline Groovy execution is all within the master JVM. Steps like sh run within a node block do things like run a process on the indicated node, but the Groovy execution is still on the master. If you want to run Groovy code on the agent, you'd be best off doing something like the below, with your Groovy script in the shared library at resources/foo.groovy (rather than vars/foo.groovy): node { writeFile(file: "script.groovy", libraryResource("foo.groovy")) sh "groovy script.groovy" } Jenkins / JENKINS-54646 External jars in shared libraries are always executed on master Change By: Andrew Bayer Status: Open Resolved Resolution: Not A Defect Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.