2013-07-31 21:23:51 -06:00
|
|
|
// 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.
|
|
|
|
|
2015-01-04 20:02:59 -07:00
|
|
|
The files in these directories constitute the continuous builder:
|
2013-07-31 21:23:51 -06:00
|
|
|
|
2015-01-04 20:02:59 -07:00
|
|
|
app/: a.k.a the "dashboard"; the App Engine code that runs http://build.golang.org/
|
2014-12-29 13:29:13 -07:00
|
|
|
buildlet/: HTTP server that runs on a VM and is told what to write to disk
|
2015-01-04 20:02:59 -07:00
|
|
|
and what command to run. This is cross-compiled to different architectures
|
2014-12-29 13:29:13 -07:00
|
|
|
and is the first program run when a builder VM comes up. It then
|
2015-01-04 20:02:59 -07:00
|
|
|
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.
|
2014-09-03 11:26:52 -06:00
|
|
|
coordinator/: daemon that runs on CoreOS on Google Compute Engine and manages
|
2015-01-04 20:02:59 -07:00
|
|
|
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.
|
2014-10-05 23:32:41 -06:00
|
|
|
watcher/: a daemon that watches for new commits to the Go repository and
|
|
|
|
its sub-repositories, and notifies the dashboard of those commits.
|
2013-07-31 21:23:51 -06:00
|
|
|
|
2015-01-04 20:02:59 -07:00
|
|
|
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.
|
2013-07-31 21:23:51 -06:00
|
|
|
|
|
|
|
|