-
Bug
-
Resolution: Unresolved
-
Major
-
None
I recently discovered that jobs which contain parameter types supported by the Active Choices plugin don't get rendered correctly when using the parameterized trigger plugin.
More specifically, when accessing the <JOB_URL>/parambuild/ URL for a particular job form elements provided by Active Choices parameters are rendered as plain-text parameters instead of their correct types. For example, choice parameters with drop down lists appear as text entry fields with no drop-down list at all.
- relates to
-
JENKINS-28735 Supporting Jobs triggered by plug-ins, API and scripts, timer
-
- Reopened
-
I attached some screen shots illustrating the problem. A simple choice parameter with a list of choices generated by a groovy script. When using the /build URL for the job, the choices are rendered correctly. When using the /parambuild URL they are not. When the parameter type is 'active choices parameter' it appears as though the Groovy script does get executed but only the first choice from the list appears in the text entry field. When the parameter type is 'active choices reactive parameter' the form element is still rendered as a text entry field but there is no default value provided.