[JIRA] (JENKINS-49457) Git Parameter does not work as input in a scripted pipeline

m@jungsbluth.de (JIRA)

unread,

Feb 8, 2018, 9:32:03 AM2/8/18

to jenkinsc...@googlegroups.com

Magnus Jungsbluth created an issue

Jenkins /

JENKINS-49457

Git Parameter does not work as input in a scripted pipeline

Issue Type:	Bug
Assignee:	Boguslaw Klimas
Components:	git-parameter-plugin
Created:	2018-02-08 14:31
Environment:	Jenkins ver. 2.89.1 Git Parameter Plugin 0.90
Priority:	Major
Reporter:	Magnus Jungsbluth

I tried to use the git parameter plugin in a pipeline script to fill an input (Target Branch to merge to in another repository).

According to https://jenkins.io/doc/pipeline/steps/pipeline-input-step/ GitParameters should work for inputs,

 
                                                                input(
  id: 'Proceed1', message: 'Specifiy QA Candiate Branch', 
  parameters: [
    [$class: 'GitParameterDefinition', 
     name: 'candidateBranch', 
     type: 'PT_BRANCH', 
     ]
  ]
) 
                                                            

This gets rendered but whatever I do the branch select stays empty (When refreshing I can see a brief spinner with "Retrieving..."). I also tried to capture related logs but couldn't get anything (From looking at the code only exceptional cases are logged).

I also tried as documented in https://jenkins.io/doc/pipeline/steps/pipeline-input-step/

 
                                                                type: 'Branch'  
                                                            

Just to validate that it works in general I added the parameter to the job itself and if I trigger a parameterized build the select is properly filled.

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

klimas7@gmail.com (JIRA)

unread,

Feb 25, 2018, 4:40:03 AM2/25/18

to jenkinsc...@googlegroups.com

Boguslaw Klimas commented on

JENKINS-49457

Re: Git Parameter does not work as input in a scripted pipeline

Hi Magnus Jungsbluth

Thanks for your request, unfortunately plugin doesn't support 'input-steps'.
I changing the issue on a feature not a bug.
I did small research and change in source code isn't simple.
I will be able to come back this issue only at the beginning of April

Regards

Bogusław