OLD | NEW |
1 Skia Buildbots | 1 Skia Buildbots |
2 ============== | 2 ============== |
3 | 3 |
4 Overview | 4 Overview |
5 -------- | 5 -------- |
6 | 6 |
7 Like the Chromium team, the Skia team uses [buildbot](http://trac.buildbot.net/) | 7 Like the Chromium team, the Skia team uses [buildbot](http://trac.buildbot.net/) |
8 to run continuous builds and tests. | 8 to run continuous builds and tests. |
9 | 9 |
10 Here is a link to our main status page: https://status.skia.org/ | 10 Here is a link to our main status page: https://status.skia.org/ |
11 | 11 |
12 There are also Skia client, compile, Android, and FYI console pages for a detail
ed | 12 There are also buildbot console pages for a detailed view of those results: |
13 view of those results: | |
14 | 13 |
15 Externally-facing: http://build.chromium.org/p/client.skia/console | 14 Externally-facing: |
16 | 15 |
17 Internally-facing: http://chromegw.corp.google.com/i/client.skia/console | 16 * http://build.chromium.org/p/client.skia/console |
18 http://chromegw.corp.google.com/i/client.skia.internal/cons
ole | 17 * http://build.chromium.org/p/client.skia.android/console |
19 \(only visible internally\) | 18 * http://build.chromium.org/p/client.skia.compile/console |
| 19 * http://build.chromium.org/p/client.skia.fyi/console |
| 20 |
| 21 Internally-facing: |
| 22 |
| 23 * http://uberchromegw.corp.google.com/i/client.skia/console |
| 24 * http://uberchromegw.corp.google.com/i/client.skia.android/console |
| 25 * http://uberchromegw.corp.google.com/i/client.skia.compile/console |
| 26 * http://uberchromegw.corp.google.com/i/client.skia.fyi/console |
| 27 * http://uberchromegw.corp.google.com/i/client.skia.internal/console |
| 28 |
20 | 29 |
21 Architecture | 30 Architecture |
22 ------------ | 31 ------------ |
23 | 32 |
24 The buildbot system consists of these elements: \(see | 33 The buildbot system consists of these elements: \(see |
25 http://buildbot.net/buildbot/docs/current/manual/introduction.html#system-archit
ecture | 34 http://buildbot.net/buildbot/docs/current/manual/introduction.html#system-archit
ecture |
26 for more detail\) | 35 for more detail\) |
27 | 36 |
28 * builder | 37 * Buildbot Master |
29 | 38 |
30 * one repeatable build and/or test configuration on a given platform. | 39 * Watches for new commits to land in the Skia repository |
31 * each builder maintains its own local checkout of the Skia repo | 40 \(https://skia.googlesource.com/skia\) |
32 * only one builder is running at any given time on any single buildslave; ot
herwise, | 41 * Whenever a new commit lands, it triggers a **Build** on each **Builder** |
33 different builders could interfere with each other's performance numbers | 42 to test the new revision. |
| 43 * Serves up status pages whenever anybody requests them |
34 | 44 |
35 * buildbot master | 45 * Build |
| 46 |
| 47 * One run of a particular **Builder**, at a particular code revision. |
| 48 * "Build" is sort of a misnomer; it's just a list of steps (typically shell |
| 49 commands) which are run by the **Buildslave** process on the host |
| 50 machine, and those may include compiling and running code as well as |
| 51 arbitrary other commands. |
| 52 |
| 53 * Builder |
| 54 |
| 55 * One repeatable build and/or test configuration on a given platform. The |
| 56 Builder is basically a blueprint which provides logic to determine which |
| 57 steps to run within a Build. |
| 58 |
| 59 * Buildslave \(or "buildbot slave"\) |
36 | 60 |
37 * watches for new commits to land in the Skia repository | 61 * A process running on a host machine that builds and runs code as directed |
38 \(https://skia.googlesource.com/skia\) | 62 by the Buildbot Master. |
39 * whenever a new commit lands, it tells buildbot slaves to start building an
d | 63 * One or more Builders may run on a given Buildslave, but only one runs at |
40 testing the latest revision | 64 a time. |
41 * serves up status pages whenever anybody requests them | 65 * One or more Buildslaves may run on a given host machine. |
42 | |
43 * buildslave \(or "buildbot slave"\) | |
44 | |
45 * a process on a machine that builds and runs code as directed by the buildb
ot | |
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 | 66 |
53 | 67 |
54 Status View | 68 Status View |
55 ------------ | 69 ------------ |
56 | 70 |
57 The status view shows a table with builders, grouped by test type and platform, | 71 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 | 72 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 | 73 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 | 74 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 | 75 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. | 76 the branch on which the commit was made is shown on the very left. |
63 | 77 |
64 For more detail, you can click on an individual cell to get a summary of the | 78 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 | 79 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. | 80 the top of each column to see a summary of recent builds for a given builder. |
67 | 81 |
68 | 82 |
69 | 83 |
70 | 84 |
OLD | NEW |