[mirror] Go's continuous build and release infrastructure (no stability promises)
Перейти к файлу
Andrew Gerrand 07e7fd5d0c dashboard/watcher: use commit date, not author date
Commit date is what is relevant to the dashboard.

Change-Id: I807492768c8f7dcbf9ee6bdc233976cb25ee8647
Reviewed-on: https://go-review.googlesource.com/1356
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2014-12-11 23:19:37 +00:00
app dashboard: tell perf dashboard about release 1.4 2014-12-11 22:29:06 +00:00
builder dashboard/builder: re-set -dash default to hg dashboard 2014-12-10 04:17:47 +00:00
coordinator tools: add import comments. 2014-12-09 22:42:16 +00:00
env dashboard/env: update linux builder Dockerfile to use git, update builder 2014-12-09 06:07:41 +00:00
updater tools: add import comments. 2014-12-09 22:42:16 +00:00
watcher dashboard/watcher: use commit date, not author date 2014-12-11 23:19:37 +00:00
README dashboard/env: add go-commit-watcher image 2014-12-01 09:59:02 -08:00

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/
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).