-
Bug
-
Resolution: Fixed
-
Minor
-
None
Dropdown options are not rendered properly in the new Declarative Directive Generator.
Steps to reproduce:
1. Go to Manage Jenkins>Global Tool Configuration>Gradle Installations and then add two or more random Gradle versions.
2. Create a Pipeline job and go to the Pipeline Syntax section at /job/PipelineName/directive-generator/.
3. Click on Declarative Directive Generator
4. Select tools: Tools from the dropdown menu.
5. Add Gradle.
You'll notice that the Version drop down has multiple items in it, but the display value is empty. If you choose one and click Generate Declarative Directive you'll notice that it will have the name of the Gradle versions you added previously depending on which empty dropdown item you choose.
The HTML sets a value for the option element, but doesn't seem to also include the name string in the <option>NAMESHOULDBEHEREBUTISNT</option> element.
- relates to
-
JENKINS-56832 Simplification of symbol-hetero-list.jelly / ToolsDirective/config.jelly
-
- In Review
-
- links to
Well, that's a weird one. It's due to SECURITY-624 having a strange interaction with the l:renderOnDemand tag. Anyway, it only is a problem with core 2.89.4 and 2.107 and greater, and I've got a PR up fixing it at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/281.