Details
-
Type:
Story
-
Status: Resolved (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Component/s: blueocean-plugin
-
Labels:
-
Similar Issues:
-
Epic Link:
-
Sprint:tethys
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
- is blocked by
-
-
- Resolved
-
-
-
- Resolved
-
-
JENKINS-39563 Basic form components
-
- Resolved
-
- is duplicated by
-
JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Open
-
(1 relates to)
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | JENKINS-38490 [ 174672 ] |
| Sprint | indian [ 126 ] |
| Link |
This issue is blocked by |
| Link |
This issue is blocked by |
| 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 |
| Sprint | indian [ 126 ] | arctic [ 131 ] |
| Sprint | arctic [ 131 ] | arctic 2 [ 136 ] |
| Sprint | arctic 2 [ 136 ] | arctic [ 131 ] |
| Sprint | arctic [ 131 ] | arctic 2 [ 136 ] |
| Sprint | tasman [ 136 ] | arctic [ 131 ] |
| Rank | Ranked higher |
| Sprint | arctic [ 131 ] | tasman [ 136 ] |
| Rank | Ranked lower |
| Assignee | Brody Maclean [ brody ] |
| Sprint | tasman [ 136 ] | indian [ 126 ] |
| Rank | Ranked lower |
| Rank | Ranked higher |
| Attachment | Input Needed Modal.png [ 34624 ] |
Zeplin Link https://zpl.io/2bLMX6
Mockup
| Assignee | Brody Maclean [ brody ] |
| Sprint | indian [ 126 ] | arctic [ 131 ] |
| Rank | Ranked higher |
| Assignee | Thorsten Scherler [ tscherler ] |
| Rank | Ranked lower |
| Sprint | arctic [ 131 ] |
| Sprint | tasman [ 136 ] |
| Rank | Ranked higher |
| Link |
This issue is blocked by |
| Sprint | tasman [ 136 ] | frank [ 156 ] |
| Sprint | frank [ 156 ] | frank 2 [ 161 ] |
| Link |
This issue is duplicated by |
| Rank | Ranked higher |
| Link |
This issue is duplicated by |
| Labels | adoption |
| 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: |
| 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! |
| Attachment | Screen Shot 2016-12-21 at 7.14.43 pm.png [ 35240 ] |
| 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! |
| Sprint | tethys [ 161 ] | christmas [ 176 ] |
| Rank | Ranked lower |
Vivek Pandey for this one can we get all the params that were given to the pipeline? I'd like to display them somewhere like I've asked on https://issues.jenkins-ci.org/browse/JENKINS-40672?focusedCommentId=281378&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-281378
James Dumay Parameters are available only after run has started and the input steps (with parameters) are in paused state. Otherwise underlying pipeline/workflow libraries do not give any ways to get these parameter definitions. Sam Van Oort do you know any ways we can get them before and after run?
Vivek Pandey Nope, that's about the size of it – you have to capture the parameters if you want the record of their values. Otherwise you'd have to make changes to the input step itself if you wanted to track more.
Sam Van Oort
added a comment - Vivek Pandey Nope, that's about the size of it – you have to capture the parameters if you want the record of their values. Otherwise you'd have to make changes to the input step itself if you wanted to track more. | Priority | Major [ 3 ] | Critical [ 2 ] |
| Sprint | christmas [ 176 ] | tethys [ 161 ] |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Link | This issue relates to JENKINS-40884 [ JENKINS-40884 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Attachment | Input Needed Modal.png [ 35422 ] |
| Attachment | Input Needed Modal.png [ 34624 ] |
Thorsten Scherler FYI brody updated the mockups here.
The feature is ready however we need to implement some basic testing before we merge
Can't wait to give it a go!!
| Status | In Progress [ 3 ] | In Review [ 10005 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Review [ 10005 ] | Resolved [ 5 ] |
Hi, I'm using Jenkins 2.46.1 with BlueOcean 1.0.1. My project has a declarative pipeline file look like:
pipeline {
agent any
parameters {
string(
name: 'test_include_groups',
defaultValue: '',
description: 'Comma separated groups of test that should be included.')
string(
name: 'test_exclude_groups',
defaultValue: 'NonRegression,Failing,Invalid',
description: 'Comma separated groups of test that should be excluded.')
}
environment {
...
}
stages {
...
}
}
I cannot figure out where is the manual trigger button for my project in BlueOcean UI. In the old UI I can do the followings:
- Trigger build remotely with default parameters
- Manually give input parameters and build manually
Can someone show me how to achieve the same as above in new BlueOcean UI? Does my Jenkinsfile correct to do that?
Hai Nguyen
added a comment - - edited Hi, I'm using Jenkins 2.46.1 with BlueOcean 1.0.1. My project has a declarative pipeline file look like:
pipeline {
agent any
parameters {
string(
name: 'test_include_groups' ,
defaultValue: '',
description: 'Comma separated groups of test that should be included.' )
string(
name: 'test_exclude_groups' ,
defaultValue: 'NonRegression,Failing,Invalid' ,
description: 'Comma separated groups of test that should be excluded.' )
}
environment {
...
}
stages {
...
}
}
I cannot figure out where is the manual trigger button for my project in BlueOcean UI. In the old UI I can do the followings:
Trigger build remotely with default parameters
Manually give input parameters and build manually
Can someone show me how to achieve the same as above in new BlueOcean UI? Does my Jenkinsfile correct to do that?
Brody Maclean add the input mockup here and redefined the description as you see fit then un-assign it