Re: Pipeline Input Step

2019-08-02 Thread Lukas Resch
Using stages { stage('input') { input { message 'Apply changes' submitterParameter 'COMMITTER' }//, parameters: [string(defaultValue: 'herp', description: '', name: 'derp')] steps { echo

Pipeline Input Step

2019-08-02 Thread Lukas Resch
n the same stage. Is anyone using this successfully and can tell me where I am wrong or confirm that the behaviour is not as intended? Versions: Jenkins 2.187 Pipeline: Input Step 2.10 Minimal pipeline for reproduction: pipeline { agent { docker { ima

Re: Jenkins Pipeline: input step filled via remote script/curl

2016-08-23 Thread Miłosz Tyborowski
Hello. I managed to resolve this issue. Hoping that someone else will benefit from my answer, let me explain how I achieved OPs target. All that Jenkis Pipeline input step needs is a properly formatted JSON and OK button caption sent to the right URL. So, the proper syntax is: curl -X POST

Jenkins Pipeline: input step filled via remote script/curl

2016-08-18 Thread Miłosz Tyborowski
Hello everyone. Recently I have been testing Jenkins Pipeline. So far it seems like a wonderful idea, however as beautiful as it looks I run into a problem, a deal-breaker for me as it turns out. I have Jenkins pipeline with an Input step, and I would like to submit this input(single string

Jenkins Pipeline: input step filled via remote script/curl

2016-08-18 Thread Miłosz Tyborowski
Hello everyone. Recently I have been testing Jenkins Pipeline. So far it seems like a wonderful idea, however as beautiful as it looks I run into a problem, a deal-breaker for me as it turns out. I have Jenkins pipeline with an Input step, and I would like to submit this input(single string

Re: 2.0 Pipeline - input step with choice param fails

2016-05-04 Thread Lionel Orellana
Cool. Gracias. On 4 May 2016 at 18:43, Antonio Muñiz wrote: > > On Sun, May 1, 2016 at 4:21 PM, Lionel Orellana > wrote: > >> Any ideas? > > > Filed https://issues.jenkins-ci.org/browse/JENKINS-34590 (there is a > workaround in a comment). > > > -- >

Re: 2.0 Pipeline - input step with choice param fails

2016-05-04 Thread Antonio Muñiz
On Sun, May 1, 2016 at 4:21 PM, Lionel Orellana wrote: > Any ideas? Filed https://issues.jenkins-ci.org/browse/JENKINS-34590 (there is a workaround in a comment). -- Antonio Muñiz Software Engineer CloudBees, Inc. -- You received this message because you are subscribed

2.0 Pipeline - input step with choice param fails

2016-05-01 Thread Lionel Orellana
Hello I got this code from the snippet generator to capture user input with a Choice Parameter: input message: 'where do you want to build this?', parameters: [[$class: 'ChoiceParameterDefinition', choices: ['ec2', 'docker'], description: '', name: 'label']] When I add it to my pipeline it

Re: Access control in pipeline input step

2016-04-28 Thread Lionel Orellana
Great. Thanks. On 28 April 2016 at 17:45, Daniel Beck wrote: > > > On 28.04.2016, at 04:23, Lionel Orellana wrote: > > > > How can I restrict who can actually approve a manual (i.e. input) step > in a pipeline? If I have a "Deploy to PROD" step I only want

Re: Access control in pipeline input step

2016-04-28 Thread Daniel Beck
> On 28.04.2016, at 04:23, Lionel Orellana wrote: > > How can I restrict who can actually approve a manual (i.e. input) step in a > pipeline? If I have a "Deploy to PROD" step I only want people with a > particular role to be able to approve. Am I going about it the wrong

Access control in pipeline input step

2016-04-27 Thread Lionel Orellana
Hi How can I restrict who can actually approve a manual (i.e. input) step in a pipeline? If I have a "Deploy to PROD" step I only want people with a particular role to be able to approve. Am I going about it the wrong way? Thanks Lionel. -- You received this message because you are