I have been using the plugin recently to develop a job that allows users dynamic control of the build parameters. While I love the options and control from the plugin, I noticed also a performance issue. When I run Jenkins on my local VM with simple Jenkins installation, the job build parameters respond fast without delay. However when I checkin my code to the server and I build the job from our remote server then the response time is terrible when I click on the various drop-downs, radio-buttons, etc. It updates the dynamic values very slowly.
I see here that the performance is an issue, but I am puzzled to see it work fast on my local VM with Jenkins. So is the issue happening when it calls the Groovy Script for that parameter? Can you explain the problem better for me and let me know if a fix is coming soon? The user experience is a bit annoying.
We are using the latest Jenkins LTS with the plugin 1.5 version.
Thanks!
I'm not sure if this is related to the fix in
JENKINS-36590(commit-6a4828b08b24034fd317bf7ad0c9f5db660087c7).I hope it's not each of active-reactive input parameters would have to go through instance.getAllItems().
None of my six active-reactive input parameters are referencing "jenkinsProject" variable name.