mirror of
https://github.com/golang/go
synced 2024-11-13 18:10:24 -07:00
eea18d959e
This aligns the naming scheme with the testing package and also lets govet work on more logging calls. R=rsc CC=golang-dev https://golang.org/cl/4001048 |
||
---|---|---|
.. | ||
builder | ||
godashboard | ||
buildcontrol.py | ||
buildcron.sh | ||
builder.sh | ||
googlecode_upload.py | ||
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: godashboard/: An AppEngine that acts as a server builder.sh, buildcontrol.sh: used by the build slaves buildcron.sh: a build loop that can be run regularly via cron If you wish to run a Go builder, please email golang-dev@googlegroups.com To set up a Go builder automatically, run buildcron.sh (you might want to read it first to see what it does). To set up a Go builder by hand: * (Optional) create a new user 'gobuild' * Edit ~gobuild/.bash_profile and add the following: export GOROOT=/gobuild/go export GOARCH=XXX export GOOS=XXX export GOBIN=/gobuild/bin export PATH=$PATH:/gobuild/bin export BUILDER=$GOOS-$GOARCH export BUILDHOST=godashboard.appspot.com * 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.) * sudo apt-get install bison gcc libc6-dev ed make * cd ~gobuild * mkdir bin * hg clone https://go.googlecode.com/hg/ $GOROOT * copy builder.sh and buildcontrol.py to ~gobuild * chmod a+x ./builder.sh ./buildcontrol.py * cd go * ../buildcontrol.py next $BUILDER (just to check that things are ok) * cd .. * ./builder.sh (You probably want to run this in a screen long term.)