-
Bug
-
Resolution: Fixed
-
Major
-
None
When trying to use ${NODE_NAME} as a value for the workspace name in a Static workspace behavior environment, and running the job the following error will output from the job:
17:15:16 Building remotely on build117 in workspace c:\trees
17:15:18 Unable to setup workspace: java.lang.Exception: Undefined workspace: ${NODE_NAME}
We used this functionality with the other Perforce Plugin as we generally do not lock our jobs to specific machines. We would like to see this behavior exist with the new plugin as well.
- is related to
-
JENKINS-19222 EnvInject undefines NODE_NAME environment variable on master
- Open