[INFO] Collecting Build Stats/Timing

Problem

Mentioned in Slack idea about collecting data on build time/timing and make sure we can track regressions/optimizations:

@jfryman What I’d like to get a better understanding of wrt CI/Packages… better understanding of how we’re going to collect data points on timing

Solution 1 - CircleCI Web interface

There is already nice looking graph in CircleCI UI showing time for recent builds:

That's what we already have and it's nice!

Solution 2 - API for custom processing

Advanced option is to use CircleCI API.
Example request: [https://circleci.com/docs/api#recent-builds-project](Recent Builds For a Single Project) outputs recent builds with needed metadata:

  ...
  "start_time" : "2013-02-12T21:33:38Z", // time build started running
  "stop_time" : "2013-02-12T21:34:01Z", // time build finished running
  "build_time_millis" : 23505,
  ...

So we can collect it/process ^^ and display on our side if needed.
Even create StackStorm sensors and rules to trigger blaming ChatOps message if build time is exceeded specified +% threshold :)

FYI @jfryman and @lakshmi-kannan

The issue names no repository files, tests, or entry points. Start by reviewing the existing CircleCI configuration and the CircleCI recent-builds API documentation; done would require an agreed design and an implemented way to collect, process, and display build timing data.