Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-31973

When using the scriptler plugin the server is responding very slow

    XMLWordPrintable

    Details

    • Similar Issues:

      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

          voolkanus Amir Sinay created issue -
          Hide
          kinow Bruno P. Kinoshita added a comment -

          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?

          Show
          kinow Bruno P. Kinoshita added a comment - 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?
          Hide
          voolkanus Amir Sinay added a comment -

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

          Show
          voolkanus Amir Sinay added a comment - Hi Bruno, It happens even if I use only the scriptler plugin by itself. As soon as he uninstalled everything goes back to normal.
          Hide
          kinow Bruno P. Kinoshita added a comment -

          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.

          Show
          kinow Bruno P. Kinoshita added a comment - 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 Bruno P. Kinoshita made changes -
          Field Original Value New Value
          Component/s dynamicparameter-plugin [ 17426 ]
          Component/s active-choices-plugin [ 20520 ]
          kinow Bruno P. Kinoshita made changes -
          Assignee Bruno P. Kinoshita [ kinow ] Dominik Bartholdi [ domi ]
          Hide
          voolkanus Amir Sinay added a comment -

          Bruno P. Kinoshita
          Dominik Bartholdi

          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!

          Show
          voolkanus Amir Sinay added a comment - Bruno P. Kinoshita Dominik Bartholdi 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!
          Hide
          ran ran S added a comment -

          Bruno P. Kinoshita
          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

          Show
          ran ran S added a comment - Bruno P. Kinoshita 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
          Hide
          domi Dominik Bartholdi added a comment -

          sorry, but I'm not able to look into this before new year...

          Show
          domi Dominik Bartholdi added a comment - sorry, but I'm not able to look into this before new year...
          Hide
          ran ran S added a comment -

          Dominik Bartholdi
          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

          Show
          ran ran S added a comment - Dominik Bartholdi 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
          Hide
          escoem Emilio Escobar added a comment -

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

          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.

          Show
          escoem Emilio Escobar added a comment - 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.
          Hide
          ran ran S added a comment -

          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

          Show
          ran ran S added a comment - 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
          Hide
          domi Dominik Bartholdi added a comment -

          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

          Show
          domi Dominik Bartholdi added a comment - 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
          Hide
          escoem Emilio Escobar added a comment -

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

          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).

          Show
          escoem Emilio Escobar added a comment - 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).
          Hide
          domi Dominik Bartholdi added a comment -

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

          Show
          domi Dominik Bartholdi added a comment - Emilio Escobar hmm, now I'm confused - you say the exact opposite of Amir Sinay . If this is not an issue with scriptler, then we should update the issue and assign it to the correct plugin/jira component
          Hide
          escoem Emilio Escobar added a comment -

          Hi Dominik Bartholdi, 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

          Show
          escoem Emilio Escobar added a comment - Hi Dominik Bartholdi , 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
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 167446 ] JNJira + In-Review [ 182735 ]

            People

            • Assignee:
              domi Dominik Bartholdi
              Reporter:
              voolkanus Amir Sinay
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated: