Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Not A Defect
-
None
-
Active Choices v1.5.3, Jenkins 2.19.2
Description
Using an AC Reference parameter rendered as a complex HTML element. The value of this parameter when passed to the build is different than the value when user is interacting with the build form.
I'm attaching an example project for testing. The complex HTML element generated from the interaction with the form is displayed and is also passed to the build.
You can easily see the disrepancy between these two values after the build is performed by reviewing the build parameters
This issue is surfacing again in some of my complex builds. Kindly asking kinow to review possible fixes. Currently the workaround is to pass this parameter to another Active Choices Reactive Reference (as in the example shown) and use that value in the build. Already complex job configuration become even more so (and features are build on bugs
)