Investigate golang/build

[chriscool]

Following discussions with @jbenet, we need a network of machines we can use to:

• run builds for various platforms
• run tests in various platforms
• run longer network/protocol tests on demand

Let's properly investigate golang/build for the above goals. Here are some steps:

• evaluate golang/build (do our homework first, figure out things on our end)
• figure out what has to change, with bradfitz' help.

[chriscool]

Some information from a quick look at the golang/build source code:

• Some things look specific to Gerrit, see https://github.com/golang/build/tree/master/gerrit and https://github.com/golang/build/blob/master/app/build/notify.go#L150
• Other things look specific to Google App Engine.
• There are some hardcoded values that should be put in config files, see https://github.com/golang/build/blob/master/build.go#L5 https://github.com/golang/build/blob/master/app/build/notify.go#L27
• It looks like the config system of the dashboard relies on the Datastore Viewer in the App Engine, see https://github.com/golang/build/blob/master/app/build/config.go

So it looks like we will have to at least make some changes to make it work with GitHub instead of Gerrit. If we don't use Google App Engine, then we will have more changes to make.

[chriscool]

Closing this in favor of https://github.com/ipfs/golang-build/issues/2