-
Bug
-
Resolution: Fixed
-
Minor
-
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
- is related to
-
JENKINS-32027 Jobs with very long configuration cause script errors in browser and extremely long loading times (10+ minutes)
-
- Resolved
-
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.