Hi Amir,

Not sure if I follow it right. Do you have the problem only when using active-choices + scriptler, or does it happen even when you are using just scriptler, without the active-choices plug-in?

Hi Bruno,
It happens even if I use only the scriptler plugin by itself. As soon as he uninstalled everything goes back to normal.

Righto. Will remove the active-choices component, as it looks like we need to fix the issue in the scriptler plug-in.

If I have some spare time I may investigate it too, since I have jobs with the active-choices-plugin + scriptler-plugin (so thanks for letting me know about this behaviour but the maintainer of the scriptler-plugin is probably the best person to fix it.

kinow
domi

Can someone please help us with this issue?? It's almost impossible to work with the system now.
Waiting 45-60 seconds for a page to load is really annoying!

kinow
Hi,

I've encountered the same issue as well.
I use Jenkins 1.627 and scriptler 2.9 (also tested on 2.7).
It can take up to a minute for the jobs to load. When i disable the plugin it runs as expected.
I've tried deleting the scripts themselves but still it is very very slow..
PLEASE help.

Thanks a lot,
Ran

domi
Thanks for the response!
I will deeply appreciate if you could find the time to help with this issue as soon as you can.

Thanks again,
Ran

I have seen this behaviour when you have this plugin combination:

• project-inheritance:1.5.3 (not reproduced in 1.5.1 as is said at https://issues.jenkins-ci.org/browse/JENKINS-23993 )
• scriptler:2.7
• uno-choice:1.2

It seems that project-inheritance:1.5.3 is doing an evaluation of every parameter of every job in the current view (includes build history) so if you have groovy dynamic parameters like one-choice the groovy will be executed.

Thanks for the update!

is there any chance to get a fix for that soon? my jobs are already dependent on these versions and i cannot downgrade.

Thanks,
Ran

so far i was not able to reproduce this - can you reproduce it on a minimal new installation?

could you please also get a thread dump while seeing this issue and make it available somewhere? https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump

Hi Dominik, this is not an issue of scriptler. This behaviour only appears if you combines:

• project-inheritance:1.5.3 (not reproduced in 1.5.1 as is said at https://issues.jenkins-ci.org/browse/JENKINS-23993 )
• uno-choice:1.2 (scriptler:2.7 is required by uno-choice)

project-inheritance ask for the default value of each parameter and in the case of uno-choice (don't know if scriptler too) runs the groovy script (with a lack of performance of the system).

escoem hmm, now I'm confused - you say the exact opposite of voolkanus. If this is not an issue with scriptler, then we should update the issue and assign it to the correct plugin/jira component

Hi domi, these are the steps to reproduce the issue:

• Install Inheritance Project plugin.
• Install Active Choice Plugin (you need scriptler too because is a requirement).
• Create a Inheritance job and add a Active Choice parameter (with a very simple groovy script that returns an array of strings).
• Save and run two or three times.
• Add a custom logger for org.biouno.unochoice.AbstractScriptableParameter
• Look for getDefaultParameterValue message at the log.

Maybe if you add a scriptler parameter you can face the issue too but currently I don't know if it's a bug at inheritance or is the expected behaviour.

There is an open issue at inheritance https://issues.jenkins-ci.org/browse/JENKINS-23993