mirror of
https://github.com/golang/go
synced 2024-10-01 07:38:32 -06:00
0a8eb31860
Currently the coordinator only handles Docker container builders. An upcoming change will add VM builders, running VMs on GCE for OpenBSD, Plan 9, Windows, etc. This change refactors the handling of the coordinator's build status in prep for VM builders. Notably, it doesn't call "docker logs" directly to get logs. It now keeps them in memory instead. Because they're then in memory, we might as well make it keep the details of the last N builds too, which we kept wanting earlier. Updates #9492 Change-Id: I6bae4a5854e7efa3f8a6186ec3670a43c98c4df2 Reviewed-on: https://go-review.googlesource.com/2262 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> |
||
|---|---|---|
| .. | ||
| app | ||
| builder | ||
| buildlet | ||
| coordinator | ||
| env | ||
| retrybuilds | ||
| updater | ||
| watcher | ||
| README | ||
// Copyright 2009 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.
The files in this directory constitute the continuous builder:
app/: an AppEngine server. The code that runs http://build.golang.org/
buildlet/: HTTP server that runs on a VM and is told what to write to disk
and what command to run. This is cross-compiled to all architectures
and is the first program run when a builder VM comes up. It then
is contacted by the coordinator to do a build.
builder/: gobuilder, a Go continuous build client
coordinator/: daemon that runs on CoreOS on Google Compute Engine and manages
builds (using the builder in single-shot mode) in Docker containers.
env/: configuration files describing the environment of builders and related binaries.
Many builders are still configured ad-hoc.
watcher/: a daemon that watches for new commits to the Go repository and
its sub-repositories, and notifies the dashboard of those commits.
If you wish to run a Go builder, please email golang-dev@googlegroups.com
To run a builder:
* Write the key ~gobuild/.gobuildkey
You need to get it from someone who knows the key.
You may also use a filename of the form .gobuildkey-$BUILDER if you
wish to run builders for multiple targets.
* Append your username and password googlecode.com credentials from
https://code.google.com/hosting/settings
to the buildkey file in the format "Username\nPassword\n".
(This is for uploading tarballs to the project downloads section,
and is an optional step.)
* Build and run gobuilder (see its documentation for command-line options).