mirror of
https://github.com/golang/go
synced 2024-10-01 09:28:37 -06:00
46e9d8e060
It looks like the partial Commits are coming from the build breakages mails. If you have commit A newer than commit B, then there are two code paths depending on which reports its build result first. For slow development, B finishes before A is committed, so when A notices a failure it checks to see if B was okay. That code path seems to be okay. For submit of back-to-back changes, typically A finishes before B, so when B notices an okay it checks to see if A failed. That code path seems to zero the Commit for A while trying to set its FailNotificationSent to true. It does (did) succeed in setting FailNotificationSent to true, it just zeroed everything else. This CL adds code to refuse to do the datastore.Put to update FailNotificationSent if the Commit info is incomplete. It also tries to ignore Num=0 records, but that may not be as important anymore. LGTM=cmang R=cmang CC=golang-codereviews https://golang.org/cl/154080043 |
||
|---|---|---|
| .. | ||
| app | ||
| builder | ||
| coordinator | ||
| env | ||
| updater | ||
| watcher | ||
| 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.
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).