| LEFT | RIGHT |
|---|
| 1 // Copyright 2009 The Go Authors. All rights reserved. | 1 // Copyright 2009 The Go Authors. All rights reserved. |
| 2 // Use of this source code is governed by a BSD-style | 2 // Use of this source code is governed by a BSD-style |
| 3 // license that can be found in the LICENSE file. | 3 // license that can be found in the LICENSE file. |
| 4 | 4 |
| 5 The files in this directory constitute the continuous builder: | 5 The files in this directory constitute the continuous builder: |
| 6 | 6 |
| 7 app/: an AppEngine server. The code that runs http://build.golang.org/ | 7 app/: an AppEngine server. The code that runs http://build.golang.org/ |
| 8 builder/: gobuilder, a Go continuous build client | 8 builder/: gobuilder, a Go continuous build client |
| 9 coordinator/: daemon that runs on CoreOS on Google Compute Engine and manages | 9 coordinator/: daemon that runs on CoreOS on Google Compute Engine and manages |
| 10 builds (using the builder in single-shot mode) in Docker containers. | 10 builds (using the builder in single-shot mode) in Docker containers. |
| 11 env/: configuration files describing the environment of builders. | 11 env/: configuration files describing the environment of builders. |
| 12 Many builders are still configured ad-hoc. | 12 Many builders are still configured ad-hoc. |
| 13 watcher/: a daemon that watches for new commits int he Go repository and | 13 watcher/: a daemon that watches for new commits to the Go repository and |
| 14 its sub-repositories, and notifies the dashboard of those commits. | 14 its sub-repositories, and notifies the dashboard of those commits. |
| 15 | 15 |
| 16 If you wish to run a Go builder, please email golang-dev@googlegroups.com | 16 If you wish to run a Go builder, please email golang-dev@googlegroups.com |
| 17 | 17 |
| 18 To run a builder: | 18 To run a builder: |
| 19 | 19 |
| 20 * Write the key ~gobuild/.gobuildkey· | 20 * Write the key ~gobuild/.gobuildkey· |
| 21 You need to get it from someone who knows the key. | 21 You need to get it from someone who knows the key. |
| 22 You may also use a filename of the form .gobuildkey-$BUILDER if you | 22 You may also use a filename of the form .gobuildkey-$BUILDER if you |
| 23 wish to run builders for multiple targets. | 23 wish to run builders for multiple targets. |
| 24 | 24 |
| 25 * Append your username and password googlecode.com credentials from | 25 * Append your username and password googlecode.com credentials from |
| 26 https://code.google.com/hosting/settings | 26 https://code.google.com/hosting/settings |
| 27 to the buildkey file in the format "Username\nPassword\n". | 27 to the buildkey file in the format "Username\nPassword\n". |
| 28 (This is for uploading tarballs to the project downloads section, | 28 (This is for uploading tarballs to the project downloads section, |
| 29 and is an optional step.) | 29 and is an optional step.) |
| 30 | 30 |
| 31 * Build and run gobuilder (see its documentation for command-line options). | 31 * Build and run gobuilder (see its documentation for command-line options). |
| 32 | 32 |
| LEFT | RIGHT |
|---|
