1 Skia Buildbots 2 ============== 3 4 Overview 5 -------- 6 7 Like the Chromium team, the Skia team uses [buildbot](http://trac.buildbot.net/) 8 to run continuous builds and tests. 9 10 Here is a link to our main status page: https://status.skia.org/ 11 12 There are also Skia client, compile, Android, and FYI console pages for a detailed 13 view of those results: 14 15 Externally-facing: http://build.chromium.org/p/client.skia/console 16 17 Internally-facing: http://chromegw.corp.google.com/i/client.skia/console 18 http://chromegw.corp.google.com/i/client.skia.internal/console 19 \(only visible internally\) 20 21 Architecture 22 ------------ 23 24 The buildbot system consists of these elements: \(see 25 http://buildbot.net/buildbot/docs/current/manual/introduction.html#system-architecture 26 for more detail\) 27 28 * builder 29 30 * one repeatable build and/or test configuration on a given platform. 31 * each builder maintains its own local checkout of the Skia repo 32 * only one builder is running at any given time on any single buildslave; otherwise, 33 different builders could interfere with each other's performance numbers 34 35 * buildbot master 36 37 * watches for new commits to land in the Skia repository 38 \(https://skia.googlesource.com/skia\) 39 * whenever a new commit lands, it tells buildbot slaves to start building and 40 testing the latest revision 41 * serves up status pages whenever anybody requests them 42 43 * buildslave \(or "buildbot slave"\) 44 45 * a process on a machine that builds and runs code as directed by the buildbot 46 master 47 * one or more builders run on each buildslave 48 49 * build 50 51 * one run of a particular builder, at a particular code revision 52 53 54 Status View 55 ------------ 56 57 The status view shows a table with builders, grouped by test type and platform, 58 on the X-axis and commits on the Y-axis. The cells are colored according to 59 the status of the build for each commit: green indicates success, red indicates 60 failure, light orange indicates an in-progress build, and white indicates that 61 no build has started yet for a given revision. Commits are listed by author, and 62 the branch on which the commit was made is shown on the very left. 63 64 For more detail, you can click on an individual cell to get a summary of the 65 steps which ran for that build. You can also click one of the white bars at 66 the top of each column to see a summary of recent builds for a given builder. 67 68 69 70 71
