optimize Job Statistics portlet

Loading every build for every job can be expensive, especially in pathologically cases with > 10k builds per job. Fortunately the portlet only needs to know that a non-zero number of builds exist and not any of their details. Problem diagnosed and fix approach proposed by Matthew Sawin [FIXED JENKINS-26879]
jenkinsci · Aug 6, 2015 · 4eff12f · 4eff12f
1 parent d3862e1
commit 4eff12f
Showing 1 changed file with 1 addition and 2 deletions.
diff --git a/src/main/java/hudson/plugins/view/dashboard/stats/StatJobs.java b/src/main/java/hudson/plugins/view/dashboard/stats/StatJobs.java
@@ -51,7 +51,6 @@ public enum HealthStatus {
 
       public static HealthStatus getHealthStatus(Job job) {
          int score = job.getBuildHealth().getScore();
-         int nBuilds = job.getBuilds().size();
          if (score < 20) {
             return HEALTH_0_TO_19;
          }
@@ -65,7 +64,7 @@ public static HealthStatus getHealthStatus(Job job) {
             return HEALTH_60_TO_79;
          }
 
-         return nBuilds != 0 ? HEALTH_OVER_80 : HEALTH_UNKNOWN;
+         return job.getFirstBuild() != null ? HEALTH_OVER_80 : HEALTH_UNKNOWN;
       }
 
       public String getIconUrl() {