akeshet@ - do you have any suggestions for the best mechanism for querying and displaying these values? Do we have any existing precedent for other builders?

Assigning this to you for now to investigate and/or reassign; feel free to assign back if you don't have cycles.

In chromite:

bin/summarize_build_stats - Looks at the recent performance of different master build types, and summarizes. (also, looks at annotations)

bin/build_time_stats - Can be configured to look at various configs, examine their timings or pass/fail rate. A lot of changes lately, this tool is evolving.


Both of these are backed by the same mysql database -- cidb. In principle you could build any service you like that queries it. Or, you could extend these scripts.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/bf26542044d0cebf40bd74de663692df9ad5ca91

commit bf26542044d0cebf40bd74de663692df9ad5ca91
Author: Steven Bennetts <stevenjb@chromium.org>
Date: Sat Mar 12 01:27:44 2016

Add '--report success' to build_time_stats to generate success rate stats.

BUG= chromium:592790 
TEST=TBD

Change-Id: I734809ed93e4a6f0cc0e2dff0452fcc9808b733a
Reviewed-on: https://chromium-review.googlesource.com/332621
Commit-Ready: Steven Bennetts <stevenjb@chromium.org>
Tested-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>

[modify] https://crrev.com/bf26542044d0cebf40bd74de663692df9ad5ca91/lib/build_time_stats.py
[modify] https://crrev.com/bf26542044d0cebf40bd74de663692df9ad5ca91/scripts/build_time_stats.py

Example build_time_stats command:

~/chromeos/chromite $ ./bin/build_time_stats --cred-dir ~/Work/prod_cidb_readonly --build-type chrome-pfq --report success --log-level warning --start-date 2016-04-25 --end-date 2016-05-01 --csv > apr_25.csv

Stats are being tracked here:

https://docs.google.com/spreadsheets/d/1JnEQNEFhnBhncv_COqLC5hQC9Ge9oMjww5Xv-7mzIks/edit#gid=0

Bulk verified