I am most interested in using the "WORKSPACE" value in the enviromental values. within my pipeline.. I use it as a base to create a staging directory from so I have a value defined such as:
def outrepo="${env.WORKSPACE}/shipping-${env.BUILD_NUMBER}"
what I am getting back from that is not what I'm expecting at all.
OUTREPO: null/shipping-152
Looks like env.WORKSPACE is being resolved as a "null" instead of the full path to the job's workspace.
Is there a different form of this I should be using? I clearly see WORKSPACE as being defined when within a shell I see that value running the shell command "env."
I could hard code it I supposed, but that kind defeats the purpose a bit....