mirror of
https://github.com/golang/go
synced 2024-11-18 23:05:06 -07:00
727ecd5ac4
This resulted in our first "ok" on the dashboard for Plan 9 with the buildlet, in 19 minutes. It only runs the std tests, and nothing else after that. Update golang/go#9491 Change-Id: Iad77a594f83bfd3fa72596bcc3057645d9c9bb4c Reviewed-on: https://go-review.googlesource.com/2523 Reviewed-by: Andrew Gerrand <adg@golang.org> |
||
|---|---|---|
| .. | ||
| app | ||
| builder | ||
| buildlet | ||
| coordinator | ||
| env | ||
| retrybuilds | ||
| types | ||
| 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 these directories constitute the continuous builder:
app/: a.k.a the "dashboard"; the App Engine 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 different architectures
and is the first program run when a builder VM comes up. It then
is contacted by the coordinator to do a build. Not all builders use
the buildlet (at least not yet).
builder/: gobuilder, a Go continuous build client. The original Go builder program.
coordinator/: daemon that runs on CoreOS on Google Compute Engine and manages
builds using Docker containers and/or VMs as needed.
env/: configuration files describing the environment of builders and related
binaries. Many builders are still configured ad-hoc, without a hermetic
environment.
retrybuilds/: a Go client program to delete build results from the dashboard (app)
types/: a Go package contain common types used by other pieces.
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 first.
There is documentation at https://golang.org/wiki/DashboardBuilders but
depending on the type of builder, we may want to run it ourselves, after you
prepare an environment description (resulting in a VM image) of it. See the env
directory.