• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: git-plugin, scm-api-plugin, workflow-cps-plugin
• Labels:

  None
• Environment:

  Jenkins LTS 2.32.3 + All plugins up to date.
  
  Pipeline: Build Step : 2.4
  Git client plugin : 2.3

1. 

   image-2019-11-20-12-19-41-513.png

   12 kB

   2019-11-20 11:19

2. 

   image-2019-11-20-12-16-59-353.png

   12 kB

   2019-11-20 11:16

3. 

   image-2019-11-20-12-15-58-712.png

   12 kB

   2019-11-20 11:15

4. 

   image-2019-11-20-12-13-40-194.png

   11 kB

   2019-11-20 11:13

[JENKINS-42971] Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts

Bertrand Latinville created issue - 2017-03-21 16:45

Bertrand Latinville made changes - 2017-03-21 16:50

Description

Original: 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.

New: 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.

Bertrand Latinville made changes - 2017-03-22 08:43

Description	Original: 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.	New: 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.
Summary	Original: Pipeline script from SCM does not expand build parameters/env Variables.	New: Pipeline script from SCM does not expand build parameters/env variables.

Collapse comment: Jesse Glick added a comment - 2017-04-06 22:44

Jesse Glick added a comment - 2017-04-06 22:44

Wrong component.

Works if you have workflow-job 2.7+.

Expand comment: Jesse Glick added a comment - 2017-04-06 22:44

Jesse Glick added a comment - 2017-04-06 22:44 Wrong component. Works if you have workflow-job 2.7+.

Jesse Glick made changes - 2017-04-06 22:44

Link

New: This issue duplicates JENKINS-28447 [ JENKINS-28447 ]

Jesse Glick made changes - 2017-04-06 22:44

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

Collapse comment: liyatikal added a comment - 2017-11-27 08:24

liyatikal added a comment - 2017-11-27 08:24

How is this bug resolved? 

I'm using Jenkins 2.73.2, pipeline job and it still doesn't work.

Is there a workaround for this?

Expand comment: liyatikal added a comment - 2017-11-27 08:24

liyatikal added a comment - 2017-11-27 08:24 How is this bug resolved?  I'm using Jenkins 2.73.2, pipeline job and it still doesn't work. Is there a workaround for this?

liyatikal made changes - 2017-11-27 08:24

Resolution	Original: Duplicate [ 3 ]
Status	Original: Resolved [ 5 ]	New: Reopened [ 4 ]

Collapse comment: liyatikal added a comment - 2017-11-27 08:43

liyatikal added a comment - 2017-11-27 08:43

The workaround that worked was to uncheck  the 'lightweight checkout'

Expand comment: liyatikal added a comment - 2017-11-27 08:43

liyatikal added a comment - 2017-11-27 08:43 The workaround that worked was to uncheck  the 'lightweight checkout'

Andrew Bayer made changes - 2018-01-12 18:35

Component/s		New: scm-api-plugin [ 18054 ]
Component/s	Original: pipeline-build-step-plugin [ 21707 ]

Load more newer events