Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
Description
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.
Attachments
Issue Links
- 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
-
Code changed in jenkins
User: Jesse Glick
Path:
changelog.html
core/src/main/java/hudson/model/Job.java
test/src/test/java/hudson/model/JobTest.java
http://jenkins-ci.org/commit/jenkins/be5cd4fd169005f50eea8ccefac4b91a9b4c503c
Log:
[FIXED JENKINS-16023] Use permalinks for as many Job.getLast*Build methods as possible.