Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-38805

User can run parametrised pipeline

    XMLWordPrintable

    Details

    • Epic Link:
    • Sprint:
      tethys
    • Similar Issues:

      Description

      Parametrised pipelines are to be supported in blue ocean.
      This means when a user presses run (either on a branch, dashboard favourite, or non multibranch button) it will need to immediately pop up asking for input. The run will not commence until input is captured. If user cancels it, no run starts.

      There is a linked design ticket for how this looks (and api)

      In scope:

      • Form to dynamically render required parameters (based on api)
      • Popup dialog
      • Providing feedback on input (validation) and when accepted, redirect to running page for the run that has commenced

      For the design (visual and more) of this, see the design ticket: https://issues.jenkins-ci.org/browse/JENKINS-38393

      Sample pipeline that requests all types of input that need to be supported:

      properties([parameters([booleanParam(defaultValue: false, description: 'this is bool', name: 'boolParam'), choice(choices: 'a\nb\nc', description: 'this is choice ', name: 'choiceThing'), text(defaultValue: 'defaultval', description: 'this is multiline', name: 'multiLIne'), password(defaultValue: 'nada', description: 'This is password', name: 'pass'), string(defaultValue: 'defaultparam', description: 'This is string param', name: 'stringParam')]), pipelineTriggers([])])
      
      echo "yeah"
      

      NOTE: to get jenkins to ask for input - you have to run this pipeline once to set the input required config in Jenkins. After that, the next time you run it, it will show the form in classic:

        Attachments

          Issue Links

            Activity

            michaelneale Michael Neale created issue -
            michaelneale Michael Neale made changes -
            Field Original Value New Value
            Epic Link JENKINS-38490 [ 174672 ]
            michaelneale Michael Neale made changes -
            Sprint indian [ 126 ]
            michaelneale Michael Neale made changes -
            Link This issue is blocked by JENKINS-38804 [ JENKINS-38804 ]
            michaelneale Michael Neale made changes -
            Link This issue is blocked by JENKINS-38393 [ JENKINS-38393 ]
            michaelneale Michael Neale made changes -
            Description Parametrised pipelines are to be supported in blue ocean.
            This means when a user presses run (either on a branch, dashboard favourite, or non multibranch button) it will need to immediately pop up asking for input. The run will not commence until input is captured. If user cancels it, no run starts.

            There is a linked design ticket for how this looks (and api)

            In scope:
            * Form to dynamically render required parameters (based on api)
            * Popup dialog
            * Providing feedback on input (validation) and when accepted, redirect to running page for the run that has commenced
            Parametrised pipelines are to be supported in blue ocean.
            This means when a user presses run (either on a branch, dashboard favourite, or non multibranch button) it will need to immediately pop up asking for input. The run will not commence until input is captured. If user cancels it, no run starts.

            There is a linked design ticket for how this looks (and api)

            In scope:
            * Form to dynamically render required parameters (based on api)
            * Popup dialog
            * Providing feedback on input (validation) and when accepted, redirect to running page for the run that has commenced

            For the design (visual and more) of this, see the design ticket: https://issues.jenkins-ci.org/browse/JENKINS-38393
            jamesdumay James Dumay made changes -
            Sprint indian [ 126 ] arctic [ 131 ]
            jamesdumay James Dumay made changes -
            Sprint arctic [ 131 ] arctic 2 [ 136 ]
            jamesdumay James Dumay made changes -
            Sprint arctic 2 [ 136 ] arctic [ 131 ]
            jamesdumay James Dumay made changes -
            Sprint arctic [ 131 ] arctic 2 [ 136 ]
            jamesdumay James Dumay made changes -
            Sprint tasman [ 136 ] arctic [ 131 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Sprint arctic [ 131 ] tasman [ 136 ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Assignee Brody Maclean [ brody ]
            jamesdumay James Dumay made changes -
            Sprint tasman [ 136 ] indian [ 126 ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            brody Brody Maclean made changes -
            Attachment Input Needed Modal.png [ 34624 ]
            brody Brody Maclean made changes -
            Assignee Brody Maclean [ brody ]
            jamesdumay James Dumay made changes -
            Sprint indian [ 126 ] arctic [ 131 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Assignee Thorsten Scherler [ tscherler ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Sprint arctic [ 131 ]
            jamesdumay James Dumay made changes -
            Sprint tasman [ 136 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Link This issue is blocked by JENKINS-39563 [ JENKINS-39563 ]
            jamesdumay James Dumay made changes -
            Sprint tasman [ 136 ] frank [ 156 ]
            jamesdumay James Dumay made changes -
            Sprint frank [ 156 ] frank 2 [ 161 ]
            jamesdumay James Dumay made changes -
            Link This issue is duplicated by JENKINS-39427 [ JENKINS-39427 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Link This issue is duplicated by JENKINS-36855 [ JENKINS-36855 ]
            jamesdumay James Dumay made changes -
            Labels adoption
            michaelneale Michael Neale made changes -
            Description Parametrised pipelines are to be supported in blue ocean.
            This means when a user presses run (either on a branch, dashboard favourite, or non multibranch button) it will need to immediately pop up asking for input. The run will not commence until input is captured. If user cancels it, no run starts.

            There is a linked design ticket for how this looks (and api)

            In scope:
            * Form to dynamically render required parameters (based on api)
            * Popup dialog
            * Providing feedback on input (validation) and when accepted, redirect to running page for the run that has commenced

            For the design (visual and more) of this, see the design ticket: https://issues.jenkins-ci.org/browse/JENKINS-38393
            Parametrised pipelines are to be supported in blue ocean.
            This means when a user presses run (either on a branch, dashboard favourite, or non multibranch button) it will need to immediately pop up asking for input. The run will not commence until input is captured. If user cancels it, no run starts.

            There is a linked design ticket for how this looks (and api)

            In scope:
            * Form to dynamically render required parameters (based on api)
            * Popup dialog
            * Providing feedback on input (validation) and when accepted, redirect to running page for the run that has commenced

            For the design (visual and more) of this, see the design ticket: https://issues.jenkins-ci.org/browse/JENKINS-38393


            Sample pipeline that requests all types of input that need to be supported:

            {noformat}
            properties([parameters([booleanParam(defaultValue: false, description: 'this is bool', name: 'boolParam'), choice(choices: 'a\nb\nc', description: 'this is choice ', name: 'choiceThing'), text(defaultValue: 'defaultval', description: 'this is multiline', name: 'multiLIne'), password(defaultValue: 'nada', description: 'This is password', name: 'pass'), string(defaultValue: 'defaultparam', description: 'This is string param', name: 'stringParam')]), pipelineTriggers([])])

            echo "yeah"
            {noformat}
            NOTE: to get jenkins to ask for input - you have to run this pipeline once to set the input required config in Jenkins. After that, the next time to run it, it will show the form in classic:

            michaelneale Michael Neale made changes -
            Description Parametrised pipelines are to be supported in blue ocean.
            This means when a user presses run (either on a branch, dashboard favourite, or non multibranch button) it will need to immediately pop up asking for input. The run will not commence until input is captured. If user cancels it, no run starts.

            There is a linked design ticket for how this looks (and api)

            In scope:
            * Form to dynamically render required parameters (based on api)
            * Popup dialog
            * Providing feedback on input (validation) and when accepted, redirect to running page for the run that has commenced

            For the design (visual and more) of this, see the design ticket: https://issues.jenkins-ci.org/browse/JENKINS-38393


            Sample pipeline that requests all types of input that need to be supported:

            {noformat}
            properties([parameters([booleanParam(defaultValue: false, description: 'this is bool', name: 'boolParam'), choice(choices: 'a\nb\nc', description: 'this is choice ', name: 'choiceThing'), text(defaultValue: 'defaultval', description: 'this is multiline', name: 'multiLIne'), password(defaultValue: 'nada', description: 'This is password', name: 'pass'), string(defaultValue: 'defaultparam', description: 'This is string param', name: 'stringParam')]), pipelineTriggers([])])

            echo "yeah"
            {noformat}
            NOTE: to get jenkins to ask for input - you have to run this pipeline once to set the input required config in Jenkins. After that, the next time to run it, it will show the form in classic:

            Parametrised pipelines are to be supported in blue ocean.
            This means when a user presses run (either on a branch, dashboard favourite, or non multibranch button) it will need to immediately pop up asking for input. The run will not commence until input is captured. If user cancels it, no run starts.

            There is a linked design ticket for how this looks (and api)

            In scope:
            * Form to dynamically render required parameters (based on api)
            * Popup dialog
            * Providing feedback on input (validation) and when accepted, redirect to running page for the run that has commenced

            For the design (visual and more) of this, see the design ticket: https://issues.jenkins-ci.org/browse/JENKINS-38393


            Sample pipeline that requests all types of input that need to be supported:

            {noformat}
            properties([parameters([booleanParam(defaultValue: false, description: 'this is bool', name: 'boolParam'), choice(choices: 'a\nb\nc', description: 'this is choice ', name: 'choiceThing'), text(defaultValue: 'defaultval', description: 'this is multiline', name: 'multiLIne'), password(defaultValue: 'nada', description: 'This is password', name: 'pass'), string(defaultValue: 'defaultparam', description: 'This is string param', name: 'stringParam')]), pipelineTriggers([])])

            echo "yeah"
            {noformat}
            NOTE: to get jenkins to ask for input - you have to run this pipeline once to set the input required config in Jenkins. After that, the next time to run it, it will show the form in classic:

             !Screen Shot 2016-12-21 at 7.14.43 pm.png|thumbnail!
            michaelneale Michael Neale made changes -
            michaelneale Michael Neale made changes -
            Description Parametrised pipelines are to be supported in blue ocean.
            This means when a user presses run (either on a branch, dashboard favourite, or non multibranch button) it will need to immediately pop up asking for input. The run will not commence until input is captured. If user cancels it, no run starts.

            There is a linked design ticket for how this looks (and api)

            In scope:
            * Form to dynamically render required parameters (based on api)
            * Popup dialog
            * Providing feedback on input (validation) and when accepted, redirect to running page for the run that has commenced

            For the design (visual and more) of this, see the design ticket: https://issues.jenkins-ci.org/browse/JENKINS-38393


            Sample pipeline that requests all types of input that need to be supported:

            {noformat}
            properties([parameters([booleanParam(defaultValue: false, description: 'this is bool', name: 'boolParam'), choice(choices: 'a\nb\nc', description: 'this is choice ', name: 'choiceThing'), text(defaultValue: 'defaultval', description: 'this is multiline', name: 'multiLIne'), password(defaultValue: 'nada', description: 'This is password', name: 'pass'), string(defaultValue: 'defaultparam', description: 'This is string param', name: 'stringParam')]), pipelineTriggers([])])

            echo "yeah"
            {noformat}
            NOTE: to get jenkins to ask for input - you have to run this pipeline once to set the input required config in Jenkins. After that, the next time to run it, it will show the form in classic:

             !Screen Shot 2016-12-21 at 7.14.43 pm.png|thumbnail!
            Parametrised pipelines are to be supported in blue ocean.
            This means when a user presses run (either on a branch, dashboard favourite, or non multibranch button) it will need to immediately pop up asking for input. The run will not commence until input is captured. If user cancels it, no run starts.

            There is a linked design ticket for how this looks (and api)

            In scope:
            * Form to dynamically render required parameters (based on api)
            * Popup dialog
            * Providing feedback on input (validation) and when accepted, redirect to running page for the run that has commenced

            For the design (visual and more) of this, see the design ticket: https://issues.jenkins-ci.org/browse/JENKINS-38393


            Sample pipeline that requests all types of input that need to be supported:

            {noformat}
            properties([parameters([booleanParam(defaultValue: false, description: 'this is bool', name: 'boolParam'), choice(choices: 'a\nb\nc', description: 'this is choice ', name: 'choiceThing'), text(defaultValue: 'defaultval', description: 'this is multiline', name: 'multiLIne'), password(defaultValue: 'nada', description: 'This is password', name: 'pass'), string(defaultValue: 'defaultparam', description: 'This is string param', name: 'stringParam')]), pipelineTriggers([])])

            echo "yeah"
            {noformat}
            NOTE: to get jenkins to ask for input - you have to run this pipeline once to set the input required config in Jenkins. After that, the next time you run it, it will show the form in classic:

             !Screen Shot 2016-12-21 at 7.14.43 pm.png|thumbnail!
            jamesdumay James Dumay made changes -
            Sprint tethys [ 161 ] christmas [ 176 ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Priority Major [ 3 ] Critical [ 2 ]
            jamesdumay James Dumay made changes -
            Sprint christmas [ 176 ] tethys [ 161 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Link This issue relates to JENKINS-40884 [ JENKINS-40884 ]
            tscherler Thorsten Scherler made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            brody Brody Maclean made changes -
            Attachment Input Needed Modal.png [ 35422 ]
            brody Brody Maclean made changes -
            Attachment Input Needed Modal.png [ 34624 ]
            tscherler Thorsten Scherler made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            tscherler Thorsten Scherler made changes -
            Status In Review [ 10005 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]

              People

              • Assignee:
                tscherler Thorsten Scherler
                Reporter:
                michaelneale Michael Neale
              • Votes:
                4 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: