[JENKINS-44073] Can't use environment variables in jenkinsfile script path for pipelines from SCM

Type: Bug
Resolution: Duplicate
Priority: Major
Component/s: pipeline
Labels:
- pipeline
- scm
Environment:
Latest Windows Server 2016 Standard
Latest Jenkins + all plugins up to date
SCM plugin: PlasticSCM Plugin

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

Benjamin Buchfink created issue - 2017-05-05 08:10

Benjamin Buchfink made changes - 2017-05-15 11:34

Labels

New: pipeline scm

Andrew Bayer made changes - 2017-08-03 18:46

Link

New: This issue duplicates ~~JENKINS-42836~~ [ ~~JENKINS-42836~~ ]

Andrew Bayer made changes - 2017-08-03 18:46

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Jenkins