The build timings provided the the cluster-stats plugin are highly skewed by a few long-running jobs - notably integration test suite runs and field deployment runs. In my case, most builds take 5 to 30 minutes to compile and unit-test. However, there are a dozen full integration testsuite runs that take most of the night to run, as well as deployment runs that can take many days to push the new products out. The numbers provided by the plugin are not useful as a result of this skewing.

ENHANCEMENT REQUEST: Add a skiplist of jobs to ignore when compiling stats.