Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: blueocean-pipeline-editor-plugin
-
Labels:
-
Similar Issues:
-
Epic Link:
-
Sprint:Blue Ocean - Candidates
Description
I've created a jenkins plugin with a bunch of pipeline steps for use in either scripted or declarative pipelines. They show up in the regular Pipeline Syntax UI in Jenkins along with the Blue Ocean Pipeline editor.
In the Pipeline Syntax UI the default values appear in the form (due to the `default="foo"` in the jelly config.xml files) however in the Blue Ocean pipeline editor the forms are always blank.
Is this a known bug with Blue Ocean pipeline editor; or is there some alternative way to specify default values for the form in the plugin so that the pipeline editor can find them?
If you want to try out the plugin yourself there's a snapshot plugin here:
https://github.com/fabric8-jenkins/fabric8-declarative-pipeline-step-functions-plugin#building
Cliff Meyers I totally did not fully read the description of the ticket. Basically at the moment the steps put it in the jelly for classic UI, so I don't think the "data" that is locked up in them will be available for the pipeline editor in blue ocean.
So this changes the nature of the ticket, basically we need to find a way to include the default values in the code, vs the UI, and surface that via the API. this is a VERY different problem, worth thinking about, but may be more effort, as it then required the plugins that provide the steps to be modified to include the default values vs Jelly.
Is this a tractable problem? it now seems much bigger than it was when we started... (and I don't think we can programmatically reliably dig things out of jelly...)