1
0
mirror of https://github.com/golang/go synced 2024-11-26 06:38:00 -07:00
go/misc/dashboard
Dave Cheney ea0292c61b misc/dashboard/builder: record build result on dashboard
This is part one of two changes intended to make it easier to debug builder failures.

runOutput allows us to control the io.Writer passed to a subcommand. The intention is to add additional debugging information before and after the build which will then be capture and sent to the dashboard.

In this proposal, the only additional information is the build status. See http://build.golang.org/log/e7b5bf435b4de1913fc61781b3295fb3f03aeb6e

R=adg
CC=golang-dev
https://golang.org/cl/7303090
2013-02-15 10:44:29 +11:00
..
app misc/dashboard: add missing return value 2013-02-11 18:01:18 +11:00
builder misc/dashboard/builder: record build result on dashboard 2013-02-15 10:44:29 +11:00
codereview misc/dashboard/codereview: add campoy to list of gophers 2013-01-14 09:54:56 +11:00
README dashboard: remove old python/bash builder, update README 2011-03-26 11:56:34 +11: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.

The files in this directory constitute the continuous builder:

godashboard/: an AppEngine server
builder/:     gobuilder, a Go continuous build client

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