-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Duplicate
-
Component/s: scm-api-plugin
-
Labels:None
-
Environment:Jenkins LTS 2.32.3 + All plugins up to date.
Pipeline: Build Step : 2.4
Git client plugin : 2.3
-
Similar Issues:
Pipeline from SCM does not expand parameters or environment variables
Steps to reproduce:
- Create a new Pipeline with a String Parameter "PIPELINE_BRANCH"
- In the pipeline definition ; Select "Pipeline Script from SCM"
- Enter the repository URL
- In branch to build, enter the parameter : ${PIPELINE_BRANCH}
- Enter your script path
- Run the job with a valid branch
An error in thrown :
hudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/${PIPELINE_BRANCH}:refs/remotes/origin/${PIPELINE_BRANCH} --prune" returned status code 128:
stdout:
${PIPELINE_BRANCH} is not replaced by its value.
Same issue with an environment variable.
Expanding parameters/variable is working fine for a freestyle or matrix job.
- duplicates
-
JENKINS-28447 CpsScmFlowDefinition does not resolve variables
-
- Resolved
-
- is duplicated by
-
JENKINS-37681 PipelineScript from SCM is not accepting Parameters as input
-
- Resolved
-
-
JENKINS-36411 Cannot access environment variable from parameterized plugin in pipeline checkout
-
- Resolved
-
- is related to
-
JENKINS-48431 Pipeline script from SCM should support build parameters using Lightweight checkout
-
- Open
-
-
JENKINS-60250 "Pipeline script from SCM": Git branch field cannot expand property from file
-
- Open
-
- relates to
-
JENKINS-42836 Build parameter not expanded in script path
-
- Resolved
-
I am still seeing this as well.