-
Bug
-
Resolution: Unresolved
-
Major
-
blueocean 1.1.4
-
-
Blue Ocean - Candidates
Scope
- Update the message so that it includes what input type Blue Ocean could not read
- Ensure we have this for parameterised jobs and input steps
- Message should look something like:
This pipeline uses unsupported input type $inputType(s). Use Jenkins Classic to resolve this parametrized build.
Problem
The error message displayed in a dialog box when attempting to run a build that uses a parameter input type unsupported by BO fails with this error message:
This pipeline uses input types that are unsupported. Use Jenkins Classic to resolve parametrized build.
The error string does not tell you the name of the offending parameter or the unsupported parameter type. Nor does it enumerate or link to a list of the supported input parameter types.
The error string is defined here:
which is coming from:
The enum of supported types is here:
- links to
[JENKINS-45524] Developer should be told which input type is not supported
Epic Link | New: JENKINS-43952 [ 181484 ] |
Summary | Original: unsupported input parameter type error needs additional information | New: Developer should be told which input type is not supported |
Description |
Original:
The error message displayed in a dialog box when attempting to run a build that uses a parameter input type unsupported by BO fails with this error message: {noformat} This pipeline uses input types that are unsupported. Use Jenkins Classic to resolve parametrized build. {noformat} The error string does not tell you the name of the offending parameter or the unsupported parameter type. Nor does it enumerate or link to a list of the supported input parameter types. The error string is defined here: https://github.com/jenkinsci/blueocean-plugin/blob/0ebd0427dae366ea6fafb2e140dcb7f283103791/blueocean-web/src/main/resources/jenkins/plugins/blueocean/web/Messages.properties#L35 which is coming from: https://github.com/jenkinsci/blueocean-plugin/blob/0ebd0427dae366ea6fafb2e140dcb7f283103791/blueocean-web/src/main/resources/jenkins/plugins/blueocean/web/Messages.properties#L35 The enum of supported types is here: https://github.com/jenkinsci/blueocean-plugin/blob/d4a615534c8f8a5e94affc1a612038be90b109f9/blueocean-core-js/src/js/parameter/index.js#L20 |
New:
*Scope* * Update the message so that it includes what input type Blue Ocean could not read {noformat} This pipeline uses unsupported input type $inputType(s). Use Jenkins Classic to resolve this parametrized build. {noformat} *Problem* The error message displayed in a dialog box when attempting to run a build that uses a parameter input type unsupported by BO fails with this error message: {noformat} This pipeline uses input types that are unsupported. Use Jenkins Classic to resolve parametrized build. {noformat} The error string does not tell you the name of the offending parameter or the unsupported parameter type. Nor does it enumerate or link to a list of the supported input parameter types. The error string is defined here: https://github.com/jenkinsci/blueocean-plugin/blob/0ebd0427dae366ea6fafb2e140dcb7f283103791/blueocean-web/src/main/resources/jenkins/plugins/blueocean/web/Messages.properties#L35 which is coming from: https://github.com/jenkinsci/blueocean-plugin/blob/0ebd0427dae366ea6fafb2e140dcb7f283103791/blueocean-web/src/main/resources/jenkins/plugins/blueocean/web/Messages.properties#L35 The enum of supported types is here: https://github.com/jenkinsci/blueocean-plugin/blob/d4a615534c8f8a5e94affc1a612038be90b109f9/blueocean-core-js/src/js/parameter/index.js#L20 |
Description |
Original:
*Scope* * Update the message so that it includes what input type Blue Ocean could not read {noformat} This pipeline uses unsupported input type $inputType(s). Use Jenkins Classic to resolve this parametrized build. {noformat} *Problem* The error message displayed in a dialog box when attempting to run a build that uses a parameter input type unsupported by BO fails with this error message: {noformat} This pipeline uses input types that are unsupported. Use Jenkins Classic to resolve parametrized build. {noformat} The error string does not tell you the name of the offending parameter or the unsupported parameter type. Nor does it enumerate or link to a list of the supported input parameter types. The error string is defined here: https://github.com/jenkinsci/blueocean-plugin/blob/0ebd0427dae366ea6fafb2e140dcb7f283103791/blueocean-web/src/main/resources/jenkins/plugins/blueocean/web/Messages.properties#L35 which is coming from: https://github.com/jenkinsci/blueocean-plugin/blob/0ebd0427dae366ea6fafb2e140dcb7f283103791/blueocean-web/src/main/resources/jenkins/plugins/blueocean/web/Messages.properties#L35 The enum of supported types is here: https://github.com/jenkinsci/blueocean-plugin/blob/d4a615534c8f8a5e94affc1a612038be90b109f9/blueocean-core-js/src/js/parameter/index.js#L20 |
New:
*Scope* * Update the message so that it includes what input type Blue Ocean could not read * Ensure we have this for parameterised jobs and input steps * Message should look something like: {noformat} This pipeline uses unsupported input type $inputType(s). Use Jenkins Classic to resolve this parametrized build. {noformat} *Problem* The error message displayed in a dialog box when attempting to run a build that uses a parameter input type unsupported by BO fails with this error message: {noformat} This pipeline uses input types that are unsupported. Use Jenkins Classic to resolve parametrized build. {noformat} The error string does not tell you the name of the offending parameter or the unsupported parameter type. Nor does it enumerate or link to a list of the supported input parameter types. The error string is defined here: https://github.com/jenkinsci/blueocean-plugin/blob/0ebd0427dae366ea6fafb2e140dcb7f283103791/blueocean-web/src/main/resources/jenkins/plugins/blueocean/web/Messages.properties#L35 which is coming from: https://github.com/jenkinsci/blueocean-plugin/blob/0ebd0427dae366ea6fafb2e140dcb7f283103791/blueocean-web/src/main/resources/jenkins/plugins/blueocean/web/Messages.properties#L35 The enum of supported types is here: https://github.com/jenkinsci/blueocean-plugin/blob/d4a615534c8f8a5e94affc1a612038be90b109f9/blueocean-core-js/src/js/parameter/index.js#L20 |
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Sprint | New: Blue Ocean 1.4 - beta 2 [ 416 ] |
Rank | New: Ranked higher |
Sprint | Original: Blue Ocean 1.4 - beta 3 [ 416 ] | New: Blue Ocean 1.4 - beta 4 [ 441 ] |
This issue bites me and prevents use of BlueO. How about telling what field is not supported any place that is visible? JS console would be OK