Using
stages {
stage('input') {
input {
message 'Apply changes'
submitterParameter 'COMMITTER'
}//, parameters: [string(defaultValue: 'herp', description:
'', name: 'derp')]
steps {
echo
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
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
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
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
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).
>
>
> --
>
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
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
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
> 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
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
11 matches
Mail list logo