[mirror] Go's continuous build and release infrastructure (no stability promises)
Перейти к файлу
Brad Fitzpatrick a6cb7e420a cmd/release: also release ppc64le binaries
Updates golang/go#17193

Change-Id: Ibd882cca4c19b4ba4cdd58f43476a149a3eb6a28
Reviewed-on: https://go-review.googlesource.com/33299
Reviewed-by: Chris Broadfoot <cbro@golang.org>
2016-11-17 19:00:21 +00:00
app build: stop testing release-branch.go1.5 2016-10-24 20:22:21 +00:00
auth all: remove extdep build tag, now that it's all out of x/tools 2015-01-21 16:18:31 +00:00
buildenv cmd/gomote, buildenv, buildlet: move config code to common places 2016-09-27 18:47:08 +00:00
buildlet cmd/gomote, buildenv, buildlet: move config code to common places 2016-09-27 18:47:08 +00:00
cmd cmd/release: also release ppc64le binaries 2016-11-17 19:00:21 +00:00
dashboard dashboard: don't test-compile mips32 yet 2016-11-12 00:35:34 +00:00
devapp devapp: add per-release issue tracker dashboard 2016-09-29 16:09:41 +00:00
doc all: remote buildlets 2015-07-07 16:45:21 +00:00
env env: add gfortran-multilib to linux builder for 386 2016-10-18 18:38:00 +00:00
envutil envutil: move dedupEnv function from gomote to new package 2015-05-21 02:13:27 +00:00
gerrit gerrit: add Auth mode to use a specific cookie file, add more methods 2016-02-08 23:00:44 +00:00
godash devapp: add median close time per create time plot 2016-09-28 18:11:19 +00:00
internal internal/httpdl: new package to download things 2016-05-03 18:14:31 +00:00
kubernetes kubernetes: add basic tests 2016-08-05 01:16:14 +00:00
livelog livelog: correct comment typo 2015-09-16 16:50:28 +00:00
pargzip pargzip: remove Writer.UseSystemGzip 2016-09-20 14:39:44 +00:00
revdial revdial: fix ABBA deadlock 2015-10-07 20:17:31 +00:00
tarutil tarutil: fix things for Dave 2015-02-01 05:03:24 +00:00
types cmd/coordinator: log per-span info to datastore also 2016-10-07 00:56:04 +00:00
AUTHORS add top-level info files 2015-01-21 17:08:52 +11:00
CONTRIBUTING.md doc: add CONTRIBUTING.md 2015-02-18 23:42:02 +00:00
CONTRIBUTORS add top-level info files 2015-01-21 17:08:52 +11:00
LICENSE add top-level info files 2015-01-21 17:08:52 +11:00
PATENTS add top-level info files 2015-01-21 17:08:52 +11:00
README all: refer to build.golang.org by HTTPS URLs only 2016-04-22 02:40:25 +00:00
build.go cmd/gomote, cmd/upload, build: add gccgo-specific TODOs and constants 2015-10-19 21:21:53 +00:00
codereview.cfg build: add codereview.cfg 2015-03-18 17:04:30 +00:00

README

This subrepository holds the source for various packages and tools that support
development of the Go programming language.

To submit changes to this repository, see http://golang.org/doc/contribute.html.

app/: a.k.a the "dashboard"; the App Engine code that runs https://build.golang.org/

cmd/:

  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.

  retrybuilds/: a Go client program to delete build results from the dashboard (app)

  upload/:  a Go program to upload to Google Cloud Storage. used by Makefiles elsewhere.

  watcher/: a daemon that watches for new commits to the Go repository and
          its sub-repositories, and notifies the dashboard of those commits.

env/:     configuration files describing the environment of builders and related
          binaries. Many builders are still configured ad-hoc, without a hermetic
          environment.

types/:   a Go package contain common types used by other pieces.


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.