-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Active Choices Plug-in 2.8.3
Jenkins 2.452.1
We have long used the active choice plugin to render our own Build with Parameters page.
It has needed a user script to work properly for a long time, but after recent updates it does not work with that either.
Expected: The rendered page shows default values. When changing from default values, the values are updated.
Actual: The rendered page shows empty checkboxes, text fields, etc. When changing parameters, the default parameters are still used during execution.
Attachments: Sample Jenkinsfile, log, screenshots of sample UI and actual UI.
- is blocked by
-
JENKINS-71909 active choice updates in wrong order (does not Cascade the values correctly)
-
- Closed
-
Hi, thanks for the detailed report. I created a new pipeline with your example, then played a bit with the returned Groovy (see screenshot).
And I believe what's happening here is that https://issues.jenkins.io/browse/JENKINS-71909?filter=14783 is affecting your script now too.
Previously, the parameters were loaded in order. So your document.getElementById would succeed as the previous parameter ("I", with the "CB_BUILDS") would have been rendered first.
This issue linked above was a tentative to optimize the rendering of parameters, by rendering them as fast as possible. Which at least sounds like a good idea, but seems like it's creating issues for several users.
I will not work on your issue for now, and instead will try to use this remaining spare time that I have today/tomorrow to revert that change.
Please, note that if this takes a bit, it's because I work on the plug-in on my spare time as volunteer, so if family/$work/summer/other OSS project issues/drawing/etc. happen, then I will come back to fix that once I have time to work on this again. But let's hope I can revert, test, and prepare a release soon.
Cheers