Details
-
Bug
-
Status: Open (View Workflow)
-
Critical
-
Resolution: Unresolved
-
Jenkins ver. 1.627
java version "1.7.0_65"
Jenkins starts as init.d service(default)
Description
When using the scriptler plugin with my Jenkins instance each time I'm trying to interact with jobs that uses this plugin I'm seeing a very slow response time from the server(sometimes up to 40 sec. to load a page).
When accessing views which do not include those jobs everything working smooth.
I tried to delete the plugin and then I see a very fast response, but again if I'll install it on the instance the response is very low.
I tried to use active choice plugin(he also requires scriptler) and dynamic parameter plugin and see the same behavior. I also tried to run the scripts locally and saw the same thing.
Attachments
Activity
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
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