Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: postbuildscript-plugin
-
Labels:None
-
Environment:Linux
-
Similar Issues:
Description
When running a groovy script the script executes with the location of the jenkins binary as working directory. I feel the execution should have the workspace directory as working directory.
Attachments
Activity
Code changed in jenkins
User: Gregory Boissinot
Path:
src/main/java/org/jenkinsci/plugins/postbuildscript/PostBuildScriptLog.java
src/main/java/org/jenkinsci/plugins/postbuildscript/service/ScriptExecutor.java
http://jenkins-ci.org/commit/postbuildscript-plugin/179a31c5da73a29ccf1d4ac54d67d92ce9a6a727
Log:
FIx JENKINS-19326
Yes that will work for me. Thanks!
If you are adding variables in the groovy shell the AbstractBuild object would be a very powerful object to have. Then I can do all kinds of useful stuff from a script file residing in the project SCM (rather than abusing the some other plugin that coincidentally grants access to that object from a script entered into jenkins).
Andreas Holmen
added a comment - Yes that will work for me. Thanks!
If you are adding variables in the groovy shell the AbstractBuild object would be a very powerful object to have. Then I can do all kinds of useful stuff from a script file residing in the project SCM (rather than abusing the some other plugin that coincidentally grants access to that object from a script entered into jenkins). I'm adding a build variable, the AbstractBuild. PR here:
https://github.com/jenkinsci/postbuildscript-plugin/pull/12
Matt Ferrante
added a comment - I'm adding a build variable, the AbstractBuild. PR here:
https://github.com/jenkinsci/postbuildscript-plugin/pull/12 
I'm afraid I can't execute the Groovy script from the workspace path. However, I could add a WORKSPACE variable, accessible from your Groovy script.
Does it suit you?