We recently migrated from Jenkins core 2.46.3 with active choice plugin 1.5.3 to Jenkins core 2.107.2 with active choice plugin 2.1.
Before the update, our jobs were working fine, but since the update, the UI using this plugin has gone much much slower.
When Jenkins has just booted, it is pretty fast. However, the longer Jenkins has been running, the slower it gets (or so it seems). After a few days running, it takes from 10 to 30 minutes to display the arguments of a "build with parameters" page. We also observed a CPU peak on the Jenkins server during that time.
We tried reverting the active choice plugin to 2.0 and even 1.5.3 - still with Jenkins core 2.107.2 but this didn't help. This is why I suspect the problem comes from a compatibility with the Jenkins core.
In the specific job that is so slow, we use about 9 parameters. Among them 7 of them are or the type Active Choices Reactive Parameter. They are running scripts referencing the first two parameters.
In general, it is also not clear to me how this plugin works in terms of which parameter gets "resolved" first, when is which script called, etc.
- Is it also something other observe?
- Is there a work around?
- Is there some document about how the plugin works internally?
This issue has become a blocker for us, that's why I am happy to provide more details for troubleshooting and even to contribute to fixing the plugin if I am given some support.
By the way, there's definitely a few issues, but this plugin is awesome! Thanks to all the contributors.