[JENKINS-34876] Git Parameters not working for Pipeline projects and Jenkinsfile from SCM - Jenkins Jira

Andreas Oetken created issue - 2016-05-17 09:40

Sebastian Mandrean added a comment - 2016-06-07 15:37

Same here!

Sebastian Mandrean added a comment - 2016-06-07 15:37 Same here!

Jonathan Strootman added a comment - 2016-07-13 21:19

Me as well. You can't pass a parameter into the `Branch specifier` field of the pipeline SCM section, can you? I tried, unsuccessfully.

Jonathan Strootman added a comment - 2016-07-13 21:19 Me as well. You can't pass a parameter into the `Branch specifier` field of the pipeline SCM section, can you? I tried, unsuccessfully.

R. Tyler Croy made changes - 2016-07-25 23:52

Field	Original Value	New Value
Workflow	JNJira [ 171076 ]	JNJira + In-Review [ 184154 ]

Boguslaw Klimas made changes - 2016-07-27 11:16

Assignee

Andreas Oetken [ enno ]

Boguslaw Klimas [ klimas7 ]

Gareth Western made changes - 2016-08-04 10:26

Link

This issue duplicates ~~JENKINS-28447~~ [ ~~JENKINS-28447~~ ]

Jesse Glick added a comment - 2016-08-16 21:03

Not a duplicate. Rather missing Pipeline integration with this plugin.

Jesse Glick added a comment - 2016-08-16 21:03 Not a duplicate. Rather missing Pipeline integration with this plugin.

Jesse Glick made changes - 2016-08-16 21:03

Labels

workflow

Mark Austin made changes - 2016-08-17 18:49

Comment

[ I observed the same problem.

I came up with a workaround, note that you need git 2.0 in order to do this...

1) I wrote a script that is executed inside of the git checkout root:

[code]
git tag -l --sort=version:refname | sort -r | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > versions.properties
[code] ]

Mark Austin made changes - 2016-08-17 18:52

Attachment

Screenshot_20160817_145201.png [ 33634 ]

Mark Austin made changes - 2016-08-17 18:56

Attachment

Screenshot_20160817_145625.png [ 33635 ]

Mark Austin added a comment - 2016-08-17 18:57

I observed the same behavior, but I came up with a hacky workaround...

I wrote a shell script that will dump git tags into a sorted list that can be ingested as a property file when using the the Extended Choice Parameter plugin.

1) Run this script in the root of your git checkout dir:

genVers.sh

git tag -l --sort=version:refname | sort -r | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > /tmp/versions.properties

2) Install the Extended Choice Parameter plugin and add it to your job
https://wiki.jenkins-ci.org/display/JENKINS/Extended+Choice+Parameter+plugin

3) Point the config to the property file you generated and set the key. See my attached example:

4) Test it

Mark Austin added a comment - 2016-08-17 18:57 I observed the same behavior, but I came up with a hacky workaround... I wrote a shell script that will dump git tags into a sorted list that can be ingested as a property file when using the the Extended Choice Parameter plugin. 1) Run this script in the root of your git checkout dir: genVers.sh git tag -l --sort=version:refname | sort -r | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > /tmp/versions.properties 2) Install the Extended Choice Parameter plugin and add it to your job https://wiki.jenkins-ci.org/display/JENKINS/Extended+Choice+Parameter+plugin 3) Point the config to the property file you generated and set the key. See my attached example: 4) Test it

Boguslaw Klimas made changes - 2016-08-17 19:28

Status

Open [ 1 ]

In Progress [ 3 ]

Scott Crooks added a comment - 2016-08-23 17:45

ganthore With your script, does this assume that the Git repo has already been checked out? I'm just wondering how to run the script before the Pipeline starts. It seems you need to run the script before the pipeline actually starts so that you can populate some variable with your desired tag. The question would be, where would the one line BASH command be executed?

Scott Crooks added a comment - 2016-08-23 17:45 ganthore With your script, does this assume that the Git repo has already been checked out? I'm just wondering how to run the script before the Pipeline starts. It seems you need to run the script before the pipeline actually starts so that you can populate some variable with your desired tag. The question would be, where would the one line BASH command be executed?

Boguslaw Klimas added a comment - 2016-08-23 19:33

Hi Guys,
I working on resolving this issue. I have prototype solution.
Which supports Pipline job.
I hope to resolved this in release 0.7.0 Releases schedule

Regards

Boguslaw Klimas added a comment - 2016-08-23 19:33 Hi Guys, I working on resolving this issue. I have prototype solution. Which supports Pipline job. I hope to resolved this in release 0.7.0 Releases schedule Regards

Anudeep Lalam made changes - 2016-08-25 14:31

Priority

Minor [ 4 ]

Critical [ 2 ]

Mark Austin added a comment - 2016-08-25 14:36 - edited

Hey Scott,

Yes that is correct. I'd have the git repo poll and then ensure that the script is executed after each poll. I know it's not ideal, but it works for now until klimas7 gets things patched up.

Mark Austin added a comment - 2016-08-25 14:36 - edited Hey Scott, Yes that is correct. I'd have the git repo poll and then ensure that the script is executed after each poll. I know it's not ideal, but it works for now until klimas7 gets things patched up.

Scott Crooks added a comment - 2016-08-25 18:08 - edited

ganthore,

Can you be a bit more detailed about your job setup? I get that the BASH command you have above will grab the list of tags, and that it will put that in a file, and that the Extended Choice parameter will read that file at build time. What I don't get is when that BASH command is executed? In Jenkins pipeline, there's no option to run a BASH script before the Extended Choice plugin grabs the list of tags.

Scott Crooks added a comment - 2016-08-25 18:08 - edited ganthore , Can you be a bit more detailed about your job setup? I get that the BASH command you have above will grab the list of tags, and that it will put that in a file, and that the Extended Choice parameter will read that file at build time. What I don't get is when that BASH command is executed? In Jenkins pipeline, there's no option to run a BASH script before the Extended Choice plugin grabs the list of tags.

Mark Austin added a comment - 2016-08-25 18:18 - edited

Hey Scott,

I guess we could just run a script like this as an alternative on the Jenkins master so that the main workspace has access to the properties file:

git ls-remote -t https://github.com/jenkinsci/github-plugin | awk '{print $2}' | cut -d '/' -f 3 | cut -d '^' -f 1 | sort -b -t . -k 1,1nr -k 2,2nr -k 3,3r -k 4,4r -k 5,5r | uniq | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > /tmp/versions.properties

That way we don't have to force Jenkins to double checkout the git repo per my older example.

There are a number of ways you could do this. The end goal is to make sure that the script runs on a regular basis or immediately after the jenkins workspace has polled the git repo.

For instance, you could have the script execute on the jenkins master directly through something as simple as a cron job.

Or, you could also try running it with a post-merge git hook in the workspace, that way it runs each time after a "git pull" occurs. Here is a basic example that you could modify for your needs:
https://gist.github.com/sindresorhus/7996717

If you're familiar with incron (http://inotify.aiken.cz/?section=incron&page=why&lang=en), you could have that daemon execute the script each time it notices a file change in the git checkout folder on the workspace.

... or just wait for this bug to get patched.

Hope this helps...

Mark Austin added a comment - 2016-08-25 18:18 - edited Hey Scott, I guess we could just run a script like this as an alternative on the Jenkins master so that the main workspace has access to the properties file: git ls-remote -t https: //github.com/jenkinsci/github-plugin | awk '{print $2}' | cut -d '/' -f 3 | cut -d '^' -f 1 | sort -b -t . -k 1,1nr -k 2,2nr -k 3,3r -k 4,4r -k 5,5r | uniq | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > /tmp/versions.properties That way we don't have to force Jenkins to double checkout the git repo per my older example. There are a number of ways you could do this. The end goal is to make sure that the script runs on a regular basis or immediately after the jenkins workspace has polled the git repo. For instance, you could have the script execute on the jenkins master directly through something as simple as a cron job. Or, you could also try running it with a post-merge git hook in the workspace, that way it runs each time after a "git pull" occurs. Here is a basic example that you could modify for your needs: https://gist.github.com/sindresorhus/7996717 If you're familiar with incron ( http://inotify.aiken.cz/?section=incron&page=why&lang=en ), you could have that daemon execute the script each time it notices a file change in the git checkout folder on the workspace. ... or just wait for this bug to get patched. Hope this helps...

Scott Crooks added a comment - 2016-08-25 20:40 - edited

ganthore We currently "solve" the problem by doing essentially what you suggested at build time using a pipeline stage:

parallel (
	getRepo1Tags: {
		sh("git ls-remote --quiet --tags --heads ${repo1GitUrl} | awk '{print \$2}' | grep -vi '{}' | cut -d/ -f1,2 --complement > ${repo1TmpTags}")
	},
	getRepo2Tags: {
		sh("git ls-remote --quiet --tags --heads ${repo2GitUrl} | awk '{print \$2}' | grep -vi '{}' | cut -d/ -f1,2 --complement > ${repo2TmpTags}")
	}
)

After that we use the "input" command in pipeline to pause the build and wait for user input.

def listofRepo1TagsBranches = readFile(repo1TmpTags).trim()
def repo1TagBranch = input([message: 'Select a Git branch / tag', parameters: [[$class: 'ChoiceParameterDefinition', choices: listofRepo1TagsBranches, description: '', name: 'Repo 1 branch / tag to build']]])

def listofRepo2TagsBranches = readFile(repo2TmpTags).trim()
def repo2TagBranch = input([message: 'Select a Git branch / tag', parameters: [[$class: 'ChoiceParameterDefinition', choices: listofRepo2TagsBranches, description: '', name: 'Repo 2 branch / tag to build']]])

This works if you're not using automated deployments. However, for our staging environments, we rely on a webhook to be called so that code is automatically pushed to staging. I'm not sure how you would parameterize this without this plugin getting updated for pipeline support. Anyway, I'll figure out another solution in the meantime.

Scott Crooks added a comment - 2016-08-25 20:40 - edited ganthore We currently "solve" the problem by doing essentially what you suggested at build time using a pipeline stage: parallel ( getRepo1Tags: { sh( "git ls-remote --quiet --tags --heads ${repo1GitUrl} | awk '{print \$2}' | grep -vi '{}' | cut -d/ -f1,2 --complement > ${repo1TmpTags}" ) }, getRepo2Tags: { sh( "git ls-remote --quiet --tags --heads ${repo2GitUrl} | awk '{print \$2}' | grep -vi '{}' | cut -d/ -f1,2 --complement > ${repo2TmpTags}" ) } ) After that we use the "input" command in pipeline to pause the build and wait for user input. def listofRepo1TagsBranches = readFile(repo1TmpTags).trim() def repo1TagBranch = input([message: 'Select a Git branch / tag' , parameters: [[$class: 'ChoiceParameterDefinition' , choices: listofRepo1TagsBranches, description: '', name: ' Repo 1 branch / tag to build']]]) def listofRepo2TagsBranches = readFile(repo2TmpTags).trim() def repo2TagBranch = input([message: 'Select a Git branch / tag' , parameters: [[$class: 'ChoiceParameterDefinition' , choices: listofRepo2TagsBranches, description: '', name: ' Repo 2 branch / tag to build']]]) This works if you're not using automated deployments. However, for our staging environments, we rely on a webhook to be called so that code is automatically pushed to staging. I'm not sure how you would parameterize this without this plugin getting updated for pipeline support. Anyway, I'll figure out another solution in the meantime.

SCM/JIRA link daemon added a comment - 2016-08-28 22:59

Code changed in jenkins
User: Boguslaw Klimas
Path:
pom.xml
src/findbugs/excludesFilter.xml
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/AbstractJobWrapper.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/AbstractProjectJobWrapper.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/JobWrapper.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/JobWrapperFactory.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/UnsupportedJobType.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/WorkflowJobWrapper.java
src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages.properties
src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages_pl.properties
src/test/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinitionTest.java
http://jenkins-ci.org/commit/git-parameter-plugin/3885d16c08943acd696a1c618d78687c4d63a0cb
Log:
JENKINS-34876 Git Parameters not working for Pipeline projects and Jenkinsfile from SCM

SCM/JIRA link daemon added a comment - 2016-08-28 22:59 Code changed in jenkins User: Boguslaw Klimas Path: pom.xml src/findbugs/excludesFilter.xml src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/AbstractJobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/AbstractProjectJobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/JobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/JobWrapperFactory.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/UnsupportedJobType.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/WorkflowJobWrapper.java src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages.properties src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages_pl.properties src/test/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinitionTest.java http://jenkins-ci.org/commit/git-parameter-plugin/3885d16c08943acd696a1c618d78687c4d63a0cb Log: JENKINS-34876 Git Parameters not working for Pipeline projects and Jenkinsfile from SCM

Boguslaw Klimas added a comment - 2016-08-28 23:11

Hi
I was created branch feature/JENKINS-34876 where I added support to pipeline job.
I was left to implement one method - perhaps is not necessary I must check it. If you want, you can build plugin from source and check it
I plan to release plugin about 10 sep

Regards
Boguslaw

Boguslaw Klimas added a comment - 2016-08-28 23:11 Hi I was created branch feature/JENKINS-34876 where I added support to pipeline job. I was left to implement one method - perhaps is not necessary I must check it. If you want, you can build plugin from source and check it I plan to release plugin about 10 sep Regards Boguslaw

Andrew Bayer made changes - 2016-08-29 17:24

Labels

workflow

pipeline workflow

Andrew Bayer made changes - 2016-08-29 17:27

Labels

pipeline workflow

pipeline

SCM/JIRA link daemon added a comment - 2016-08-31 22:20

Code changed in jenkins
User: Boguslaw Klimas
Path:
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/AbstractProjectJobWrapper.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/JobWrapper.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/WorkflowJobWrapper.java
src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages.properties
src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages_pl.properties
http://jenkins-ci.org/commit/git-parameter-plugin/5fc8a95ef5d23d704ca4e60ff668671be924ee20
Log:
JENKINS-34876 Git Parameters not working for Pipeline projects and Jenkinsfile from SCM

SCM/JIRA link daemon added a comment - 2016-08-31 22:20 Code changed in jenkins User: Boguslaw Klimas Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/AbstractProjectJobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/JobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/WorkflowJobWrapper.java src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages.properties src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages_pl.properties http://jenkins-ci.org/commit/git-parameter-plugin/5fc8a95ef5d23d704ca4e60ff668671be924ee20 Log: JENKINS-34876 Git Parameters not working for Pipeline projects and Jenkinsfile from SCM

SCM/JIRA link daemon added a comment - 2016-08-31 22:28

Code changed in jenkins
User: klimas7
Path:
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java
http://jenkins-ci.org/commit/git-parameter-plugin/b9c7ef390108df624f14c88a45b0be5156ebfe86
Log:
JENKINS-34876 Git Parameters not working for Pipeline projects and Jenkinsfile from SCM

SCM/JIRA link daemon added a comment - 2016-08-31 22:28 Code changed in jenkins User: klimas7 Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java http://jenkins-ci.org/commit/git-parameter-plugin/b9c7ef390108df624f14c88a45b0be5156ebfe86 Log: JENKINS-34876 Git Parameters not working for Pipeline projects and Jenkinsfile from SCM

Boguslaw Klimas made changes - 2016-08-31 22:30

Status

In Progress [ 3 ]

In Review [ 10005 ]

SCM/JIRA link daemon added a comment - 2016-08-31 22:50

Code changed in jenkins
User: Boguslaw Klimas
Path:
pom.xml
src/findbugs/excludesFilter.xml
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/AbstractJobWrapper.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/AbstractProjectJobWrapper.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/JobWrapper.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/JobWrapperFactory.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/UnsupportedJobType.java
src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/WorkflowJobWrapper.java
src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages.properties
src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages_pl.properties
src/test/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinitionTest.java
http://jenkins-ci.org/commit/git-parameter-plugin/9b1243d06a5af91494417c8cd697d14af4669bf7
Log:
Merge pull request #36 from jenkinsci/feature/JENKINS-34876

Feature/jenkins 34876

Compare: https://github.com/jenkinsci/git-parameter-plugin/compare/f047198dda1e...9b1243d06a5a

SCM/JIRA link daemon added a comment - 2016-08-31 22:50 Code changed in jenkins User: Boguslaw Klimas Path: pom.xml src/findbugs/excludesFilter.xml src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/AbstractJobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/AbstractProjectJobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/JobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/JobWrapperFactory.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/UnsupportedJobType.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/WorkflowJobWrapper.java src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages.properties src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages_pl.properties src/test/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinitionTest.java http://jenkins-ci.org/commit/git-parameter-plugin/9b1243d06a5af91494417c8cd697d14af4669bf7 Log: Merge pull request #36 from jenkinsci/feature/ JENKINS-34876 Feature/jenkins 34876 Compare: https://github.com/jenkinsci/git-parameter-plugin/compare/f047198dda1e...9b1243d06a5a

Anudeep Lalam added a comment - 2016-09-12 07:08

Hi,

When can we expect the release of Git Parameter Plugin latest version i.e. 0.7.0

Anudeep Lalam added a comment - 2016-09-12 07:08 Hi, When can we expect the release of Git Parameter Plugin latest version i.e. 0.7.0

Boguslaw Klimas added a comment - 2016-09-12 07:40

Hi,
I didn't have enough time in weekend, I'll do it today.
Sorry, for that

Regards
Boguslaw

Boguslaw Klimas added a comment - 2016-09-12 07:40 Hi, I didn't have enough time in weekend, I'll do it today. Sorry, for that Regards Boguslaw

Anudeep Lalam added a comment - 2016-09-12 09:02

Hi klimas7,

Thanks for the prompt response..

Anudeep Lalam added a comment - 2016-09-12 09:02 Hi klimas7 , Thanks for the prompt response..

Boguslaw Klimas added a comment - 2016-09-12 19:56

Release 0.7.0

Boguslaw Klimas added a comment - 2016-09-12 19:56 Release 0.7.0

Boguslaw Klimas made changes - 2016-09-12 19:56

Resolution		Fixed [ 1 ]
Status	In Review [ 10005 ]	Resolved [ 5 ]

Yan Wang added a comment - 2016-09-13 07:20

I just tried 0.7.0 and I can choose git branches and tags in the drop down.

But I failed to use it as a variable in * Branch Specifier*, seems the variable is not parsed at all.

Yan Wang added a comment - 2016-09-13 07:20 I just tried 0.7.0 and I can choose git branches and tags in the drop down. But I failed to use it as a variable in * Branch Specifier*, seems the variable is not parsed at all.

Yan Wang made changes - 2016-09-13 07:20

Attachment

Selection_104.png [ 33910 ]

Boguslaw Klimas made changes - 2016-09-13 08:46

Attachment

screenshot-1.png [ 33911 ]

Boguslaw Klimas made changes - 2016-09-13 08:47

Attachment

screenshot-2.png [ 33912 ]

Boguslaw Klimas made changes - 2016-09-13 08:49

Attachment

screenshot-3.png [ 33913 ]

Boguslaw Klimas added a comment - 2016-09-13 08:52

Hi, wyvernnot
I have configured a simple job:
Parameter:

Git Config:

And job work fine

Could you get me something more information? About your configuration.

Regards
Boguslaw

Boguslaw Klimas added a comment - 2016-09-13 08:52 Hi, wyvernnot I have configured a simple job: Parameter: Git Config: And job work fine Could you get me something more information? About your configuration. Regards Boguslaw

Yan Wang made changes - 2016-09-13 14:13

Attachment

pipeline.PNG [ 33919 ]

Yan Wang made changes - 2016-09-13 14:14

Attachment

params.PNG [ 33920 ]

Yan Wang added a comment - 2016-09-13 14:17

Hi, I am using Jenkins@2.7.4 with a pipeline project.

here is the params settings

here is the pipeline settings

Yan Wang added a comment - 2016-09-13 14:17 Hi, I am using Jenkins@2.7.4 with a pipeline project. here is the params settings here is the pipeline settings

Yan Wang added a comment - 2016-09-13 14:36

Oh, I just tried String Parameters and it does not work neither.

So I guess the problem is not with Git Parameter plugin but SCM plugin.

Related issue is: https://issues.jenkins-ci.org/browse/JENKINS-34540

Yan Wang added a comment - 2016-09-13 14:36 Oh, I just tried String Parameters and it does not work neither. So I guess the problem is not with Git Parameter plugin but SCM plugin. Related issue is: https://issues.jenkins-ci.org/browse/JENKINS-34540

Minh Chung added a comment - 2017-08-04 22:06

klimas7 Thank you for working on this ticket. I apologize for bringing it back up but I was wondering would it be possible to parametize git branches from the checkouts done in the Jenkinsfile pipeline? I was able to get this this to work in the Pipeline for the primary git source but my Jenkinsfile has additional git sources I also need to check out and would like to parametize those git source branches for selection.

Minh Chung added a comment - 2017-08-04 22:06 klimas7 Thank you for working on this ticket. I apologize for bringing it back up but I was wondering would it be possible to parametize git branches from the checkouts done in the Jenkinsfile pipeline? I was able to get this this to work in the Pipeline for the primary git source but my Jenkinsfile has additional git sources I also need to check out and would like to parametize those git source branches for selection.

Julian Mosquera added a comment - 2019-07-24 01:15

it looks like is a problem in scripted pipeline. When i changed the script to declarative it worked

Julian Mosquera added a comment - 2019-07-24 01:15 it looks like is a problem in scripted pipeline. When i changed the script to declarative it worked

JJ Ruescas added a comment - 2019-08-12 20:08

julian_linux, were you able to get it fixed. I'm experiencing a similar issue.

JJ Ruescas added a comment - 2019-08-12 20:08 julian_linux , were you able to get it fixed. I'm experiencing a similar issue.

Nick Nieslanik added a comment - 2019-10-29 17:30 - edited

Hi! I am using Jenkins LTS 2.190.2 via Docker container and I'm experiencing this issue using a SCM declarative pipeline. I have an Extensible Choice param in the job that is letting me pick a branch, and then I am referring to the branch variable selection as

${webapp_branch}

in the pipeline settings for the Jenkinsfile in SCM (specifically GIT). Based on my reading of this issue, it seems as if folks think this is fixed? I am definitely able to repo consistently across a number of declarative pipeline jobs on my server. I have config extremely similar to wyvernnot's screenshots from 2016. klimas7 Any insight here?

Screenshots:

choice settings

pipeline settings

Error from build:

hudson.plugins.git.GitException: Command "git fetch --tags --progress --prune -- origin +refs/heads/${webapp_branch}:refs/remotes/origin/${webapp_branch}" returned status code 128:
stdout: 
stderr: fatal: Couldn't find remote ref refs/heads/${webapp_branch}	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2174)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1866)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:78)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:547)
	at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:358)
	at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:197)
	at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:173)
	at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:113)
	at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:299)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:429)
Finished: FAILURE

Nick Nieslanik added a comment - 2019-10-29 17:30 - edited Hi! I am using Jenkins LTS 2.190.2 via Docker container and I'm experiencing this issue using a SCM declarative pipeline. I have an Extensible Choice param in the job that is letting me pick a branch, and then I am referring to the branch variable selection as ${webapp_branch} in the pipeline settings for the Jenkinsfile in SCM (specifically GIT). Based on my reading of this issue, it seems as if folks think this is fixed? I am definitely able to repo consistently across a number of declarative pipeline jobs on my server. I have config extremely similar to wyvernnot 's screenshots from 2016. klimas7 Any insight here? Screenshots: choice settings pipeline settings Error from build: hudson.plugins.git.GitException: Command "git fetch --tags --progress --prune -- origin +refs/heads/${webapp_branch}:refs/remotes/origin/${webapp_branch}" returned status code 128: stdout: stderr: fatal: Couldn't find remote ref refs/heads/${webapp_branch} at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2174) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1866) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:78) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:547) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:358) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:197) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:173) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:113) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:299) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE

Ievgen added a comment - 2021-06-07 15:36

Hi there. Got the same issue again. Git tag parameter been not delivered to git checkout action.
Jenkins:Jenkins 2.289.1
Parameter plugin:

0.9.13

Ievgen added a comment - 2021-06-07 15:36 Hi there. Got the same issue again. Git tag parameter been not delivered to git checkout action. Jenkins: Jenkins 2.289.1 Parameter plugin: 0.9.13

Ievgen made changes - 2021-06-07 15:36

Resolution	Fixed [ 1 ]
Status	Resolved [ 5 ]	Reopened [ 4 ]

Jenkins

Git Parameters not working for Pipeline projects and Jenkinsfile from SCM

Details

Description

Attachments

Attachments

Issue Links

Activity

People

Dates