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

Script timeout during start of configure a jenkins job

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • Suse Linux 11 Sp2, Oracle Java 1.7.0_45, jenkins with internal web interface, Mozilla FireFox 37.0.1 on Windows 7

      I updated jenkins from version 1.596 to version 1.609.
      No I get a script timeout if I try to configure some of the larger jobs.
      I can configure small jobs without any problems.
      I increase the firefox script timeout from 10 seconds to 100 seconds.
      Now I can configure the jenkins jobs, but it takes a very long time to start editing.
      With version 1.596 it was possible to start configuring of the same larger jobs in the predefined timout of 10 seconds

          [JENKINS-27948] Script timeout during start of configure a jenkins job

          Brian Ray added a comment - - edited

          Our upgrade to 1.609.1 seems to be exhibiting the same JS timeouts on an admittedly too-big job config, regardless of the number of builds. The timeouts usually happen in codemirror.js. New to JIRA and am wondering if adding a copy of the config scrubbed of proprietary information will help. I can gather other information about our install as well: plugins, client and server attributes, etc.

          Luckily the workaround of setting JS timeouts in Firefox is working. (32 bit Windows v38.0.5, all three dom.max_*_script_run_time params set to 120.) The page is coming up somewhere in the neighborhood of 100 seconds.

          If it would help to attach our bits of evidence, let me know.

          Brian Ray added a comment - - edited Our upgrade to 1.609.1 seems to be exhibiting the same JS timeouts on an admittedly too-big job config, regardless of the number of builds. The timeouts usually happen in codemirror.js. New to JIRA and am wondering if adding a copy of the config scrubbed of proprietary information will help. I can gather other information about our install as well: plugins, client and server attributes, etc. Luckily the workaround of setting JS timeouts in Firefox is working. (32 bit Windows v38.0.5, all three dom.max_*_script_run_time params set to 120.) The page is coming up somewhere in the neighborhood of 100 seconds. If it would help to attach our bits of evidence, let me know.

          I can configure small jobs without any problems.
          I increase the firefox script timeout from 10 seconds to 100 seconds.
          Now I can configure the jenkins jobs, but it takes a very long time to start editing.

          Same issue with LTS 1.609.1 & LTS 1.625.1 too.

          Dilip Mahadevappa added a comment - I can configure small jobs without any problems. I increase the firefox script timeout from 10 seconds to 100 seconds. Now I can configure the jenkins jobs, but it takes a very long time to start editing. Same issue with LTS 1.609.1 & LTS 1.625.1 too.

          Scott Hebert added a comment -

          We were able to workaround this by doing the following:

          Navigate to:

          • Manage Jenkins
          • Configure Global Security
          • In the Markup Formatter section, ensure:
            • Safe HTML is selected
            • Click on Disable syntax highlighting

          With this change, we went from a config page load that would timeout in Firefox to one that loads in under 20s.

          Scott Hebert added a comment - We were able to workaround this by doing the following: Navigate to: Manage Jenkins Configure Global Security In the Markup Formatter section, ensure: Safe HTML is selected Click on Disable syntax highlighting With this change, we went from a config page load that would timeout in Firefox to one that loads in under 20s.

          Suggestion above by @scotthebert works.

          Yeong Sheng Tan added a comment - Suggestion above by @scotthebert works.

          Reiner Wirtz added a comment -

          I have a jenkins job, which has about 20 steps.
          Every step has a condition depending on a expression with jenkins variables.
          About 15 of the steps call simple a unix shell script, two others system groovy scripts.
          The size of the unix shell scripts vary from 5 to 30 lines.

          To open this job for configure takes more than 2 minutes.
          I haven't seen a difference in time if I use the workaround mentioned by Scott Hebert or not.

          Reiner Wirtz added a comment - I have a jenkins job, which has about 20 steps. Every step has a condition depending on a expression with jenkins variables. About 15 of the steps call simple a unix shell script, two others system groovy scripts. The size of the unix shell scripts vary from 5 to 30 lines. To open this job for configure takes more than 2 minutes. I haven't seen a difference in time if I use the workaround mentioned by Scott Hebert or not.

          Chris Cralle added a comment -

          There is a problem with CodeMirror and textarea windows.
          I just upgraded to LTS 1.642.3 this weekend and getting a little rubbing from my comrades about how long the configure load times are.
          I have one 2x4 Matrix multi-step job with conditionals that have shell, python, and windows batch executes. The configure page for this job generates 8-10 timeouts in codemirror.js and takes minutes to load.
          Common timeouts are on lines 1247, 1207, 853
          These deal with the gutter and scrollbar as far as I can tell.

          I've spent Saturday trying everything I can to somehow just DISABLE codemirror. But since it's core, not a plugin, and there's no exposed configuration for it, I'm pretty much stuck with it's behavior. Is it possible to turn it off?
          The setting in security for syntax highlighting is not related, the number of builds or history is not related. This is purely codemirror barfing on complex jobs with recursive textareas.

          I'm surprised codemirror is not a tag/label on this ticket.

          I am creating a sanitized config.xml which I hope to upload to this ticket in the hope that it helps with a resolution.

          Chris Cralle added a comment - There is a problem with CodeMirror and textarea windows. I just upgraded to LTS 1.642.3 this weekend and getting a little rubbing from my comrades about how long the configure load times are. I have one 2x4 Matrix multi-step job with conditionals that have shell, python, and windows batch executes. The configure page for this job generates 8-10 timeouts in codemirror.js and takes minutes to load. Common timeouts are on lines 1247, 1207, 853 These deal with the gutter and scrollbar as far as I can tell. I've spent Saturday trying everything I can to somehow just DISABLE codemirror. But since it's core, not a plugin, and there's no exposed configuration for it, I'm pretty much stuck with it's behavior. Is it possible to turn it off? The setting in security for syntax highlighting is not related, the number of builds or history is not related. This is purely codemirror barfing on complex jobs with recursive textareas. I'm surprised codemirror is not a tag/label on this ticket. I am creating a sanitized config.xml which I hope to upload to this ticket in the hope that it helps with a resolution.

          Carlos Moro added a comment -

          I followed the instructions from Scott (Global Security -> In the Markup Formatter section, ensure: Safe HTML is selected and Click on Disable syntax highlighting) and now I can configure jobs in Firefox, but Chrome and Safari are still broken. At least we have a workaround.

          Carlos Moro added a comment - I followed the instructions from Scott (Global Security -> In the Markup Formatter section, ensure: Safe HTML is selected and Click on Disable syntax highlighting) and now I can configure jobs in Firefox, but Chrome and Safari are still broken. At least we have a workaround.

          hai li added a comment -

          Any idea on how to turn off codemirror to bypass this issue?

          hai li added a comment - Any idea on how to turn off codemirror to bypass this issue?

          Reiner Wirtz added a comment -

          Hello,

          it seems that the bug is fixed.
          I have two jobs, which took about 10 minutes to open for edit with jenkins up to 2.11
          Since I use 2.12 the same jobs takes about 10 to 20 seconds to open for edit.
          And the browser does'n allocated about 10 GB of memory to open the job any more.

          Reiner Wirtz added a comment - Hello, it seems that the bug is fixed. I have two jobs, which took about 10 minutes to open for edit with jenkins up to 2.11 Since I use 2.12 the same jobs takes about 10 to 20 seconds to open for edit. And the browser does'n allocated about 10 GB of memory to open the job any more.

          Daniel Beck added a comment -

          Resolved as JENKINS-32027 in 2.12.

          Daniel Beck added a comment - Resolved as JENKINS-32027 in 2.12.

            Unassigned Unassigned
            rw250155 Reiner Wirtz
            Votes:
            6 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: