Tidhar Klein Orbach
2016-05-11 03:46:52
From the Groovy plugin page:
Groovy Script vs System Groovy Script The plain "Groovy Script" is run in a forked JVM, on the slave where the build is run. It's the basically the same as running the "groovy" command and pass in the script. The system groovy script, OTOH, runs inside the Jenkins master's JVM. Thus it will have access to all the internal objects of Jenkins, so you can use this to alter the state of Jenkins. It is similar to the Jenkins Script Console functionality.
When not using the system Groovy, you do not have Jenkins object in your classpath. You need to make sure the required classes are accessible from the job you are running, and pass them in the "Class path" field of the "execute groovy script" step.
热门帖子
9
where should the path conent reside, on the slave itself or in another place? My code should run on the slave, so if I understand you correctly I just have to avoid using "import jenkins.model.Jenkins"?
The path should be on the slave machine. it means that you need to copy all required jar files to the slave. it seems that you will require to copy quite a few jar files - I haven't tried but you might want to create a custom tool that would deploy the jars to your slaves. Still, you might want to consider moving to the system groovy, since you get all those classes for "free"
Changing to system groovy fixed the problem. Thanks!