-
Improvement
-
Resolution: Duplicate
-
Minor
-
None
The groovy script is executed always on the master, although the job is executed on a slave. This can be an issue, if you want to access to the files checked out from the source control, like in my case, I want to inject some values contained in the source code, but I can't, because the groovy script is executed on the master and not on the slave, where the source code files are.
- duplicates
-
JENKINS-43864 EnvInject plugin documentation should explicitly say that Groovy scripts run on master
- Open