Like the Chromium team, the Skia team uses buildbot to run continuous builds and tests.
Here is a link to our main status page: https://status.skia.org/
There are also Skia client, compile, Android, and FYI console pages for a detailed view of those results:
Externally-facing: http://build.chromium.org/p/client.skia/console
Internally-facing: http://chromegw.corp.google.com/i/client.skia/console http://chromegw.corp.google.com/i/client.skia.internal/console (only visible internally)
The buildbot system consists of these elements: (see http://buildbot.net/buildbot/docs/current/manual/introduction.html#system-architecture for more detail)
builder
buildbot master
buildslave (or “buildbot slave”)
build
The status view shows a table with builders, grouped by test type and platform, on the X-axis and commits on the Y-axis. The cells are colored according to the status of the build for each commit: green indicates success, red indicates failure, light orange indicates an in-progress build, and white indicates that no build has started yet for a given revision. Commits are listed by author, and the branch on which the commit was made is shown on the very left.
For more detail, you can click on an individual cell to get a summary of the steps which ran for that build. You can also click one of the white bars at the top of each column to see a summary of recent builds for a given builder.