[JIRA] (JENKINS-57930) Pipeline script from SCM does not expand build parameters/env variables for declarative pipeline with yamlFile specified

[hanbingxi...@gmail.com (JIRA)]

Title: Message Title

jubel han updated an issue   Jenkins / JENKINS-57930 Pipeline script from SCM does not expand build parameters/env variables for declarative pipeline with yamlFile specified Change By: jubel han Reproduce step: 1. Create a parameterized pipeline job. 2. Add the string parameter called `branch` 2. Configure the pipeline definition to `Get Pipeline script from SCM`. 3. Update the section of `Branches to build` to `*/${branch}` as the parameter added above. 4. Add the following code to the file `Jenkinsfile`. {code:groovy} pipeline {     agent {         kubernetes {             label 'jks-builds'             yamlFile 'path/to/podTemplate.yaml'         }     }     stages {         stage('test') {             steps {                  echo "test"         }     } } {code} with the above reproducing steps you will get the following failed messages: ``` {code:java} hudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/${branch}:refs/remotes/origin/${branch} --prune" returned status code 128: stdout: stderr: fatal: Couldn't find remote ref refs/heads/${branch} ``` {code} however, it works if you remove the directive of `yamlFile` or using the raw yaml string instead. Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199904.1560151841000.24194.1560152040303%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.