-
Bug
-
Resolution: Fixed
-
Major
After a period of inactivity or when the JVM decides to run GC loading the dashboard can easily take longer than 1-2 minutes. Please see attached stacktrace.
- depends on
-
JENKINS-16089 Standard view columns interact force builds to be eagerly loaded
-
- Resolved
-
-
JENKINS-18846 New lazy loading permalinks can break job.lastStableBuild != null => job.lastSuccessfulBuild != null
-
- Resolved
-
- is related to
-
JENKINS-18196 With lazy-build loading estimated build duration may become expensive
-
- Resolved
-
-
JENKINS-8754 ROADMAP: Improve Start-up Time
-
- Closed
-
-
JENKINS-20989 PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered
-
- Resolved
-
I suspect this is actually caused by the massive amount of build history we had for some jobs. After enabling fine logging on hudson.model.RunMap it was obvious which jobs were causing Jenkins to hang. I have now configured discard old builds for the jobs, will report back if it helped or not.