Major PlasticSCM requires a system-wide unique workspace name. Therefore we use workspaces like "Pipelines_${NODE_NAME}" for check-out.
When specifying the jenkinsfile (Script Path) for a pipeline job configuration the ${NODE_NAME} placeholder is not evaluated correctly.
Please see the attached inital_config.png for a pipeline configuration using PlasticSCM.
When the job is run, there will be an ERROR: Jenkinsfile not found. As seen in attached error.png.
- duplicates
-
JENKINS-42836 Build parameter not expanded in script path
-
- Resolved
-
