Introduction

This page lists details of the various builders assigned to the build.golang.org CI system

New-style Builders

See http://golang.org/s/builderplan

titledescriptionownernotes
linux-386buildlet VM on GCEbradfitz
linux-386-387buildlet VM on GCEbradfitzGO386=387
linux-386-clangin Docker on GCEbradfitzDebian wheezy + clang 3.5 instead of gcc
linux-386-gccgoin Docker on GCEcmangbuilds gccgo
linux-386-sidin Docker on GCEbradfitzDebian sid
linux-amd64buildlet VM on GCEbradfitz
linux-amd64-clangin Docker on GCEbradfitzDebian wheezy + clang 3.5 instead of gcc
linux-amd64-gccgoin Docker on GCEcmangbuilds gccgo
linux-amd64-nocgoin Docker on GCEbradfitzcgo disabled
linux-amd64-nooptbuildlet VM on GCEbradfitzoptimizations and inlining disabled
linux-amd64-racebuildlet VM Docker on GCEbradfitz
linux-amd64-sidin Docker on GCEbradfitzDebian sid
linux-ppc64le-canonicalPOWER8 little endian@davecheneyUbuntu 14.04
nacl-386in Docker on GCEbradfitz
nacl-amd64p32in Docker on GCEbradfitz
openbsd-amd64-gce56buildlet VM on GCEbradfitzUsing buildlet; OpenBSD 5.6; GCE VM is built from script in build/env/openbsd-amd64
openbsd-386-gce56buildlet VM on GCEbradfitzUsing buildlet; OpenBSD 5.6; GCE VM is built from script in build/env/openbsd-386
plan9-386-gcepartialbuildlet VM on GCEbradfitzUsing buildlet; Plan 9 from 0intro; GCE VM is built from script in build/env/plan9-386; runs with GOTESTONLY=std (only stdlib tests)
freebsd-amd64-gce101buildlet VM on GCEbradfitzUsing buildlet; FreeBSD 10.1; GCE VM is built from script in build/env/freebsd-amd64
freebsd-386-gce101buildlet VM on GCEbradfitzUsing buildlet; FreeBSD 10.1; same VM image as freebsd-amd64-gce101, but builds run with GOARCH=386
freebsd-amd64-racebuildlet VM on GCEbradfitzUsing buildlet; FreeBSD 10.1; same VM image as freebsd-amd64-gce101, but runs src/race.bash instead, and n1-highcpu-4 instance type
windows-386-gcebuildlet VM on GCEbradfitz
windows-amd64-gcebuildlet VM on GCEbradfitz
windows-amd64-racebuildlet VM on GCEbradfitzOnly runs -race tests (./race.bat)

Legacy Builders

These builders are configured and run manually. The goal is to migrate as many as possible over to the new system.

titledescriptionownernotes
android-arm-crawshawNexus 7crawshawBuilder runs on attached desktop, uses adb
darwin-amd642011 Mac Mini, 2.4Ghz Core i5adgMac OS X 10.6 (10K549)
darwin-amd64-cheney2011 Mac Mini, 2.4Ghz Core i5Dave CheneyMac OS X 10.10 XCode 5
darwin-amd64-race-cheney2011 Mac Mini, 2.4Ghz Core i5Dave CheneyMac OS X 10.10 XCode 5
darwin-3862011 Mac Mini, 2.4Ghz Core i5adgMac OS X 10.6 (10K549)
darwin-386-cheney2011 Mac Mini, 2.4Ghz Core i5Dave CheneyMac OS X 10.10 XCode 5
dragonfly-amd64?Justin Sherrill?
linux-arm-luitvdRaspberryPiLuit van Drongelen
linux-arm-arm5QNAP TS-119P, ARMv5 @ 2.0GHz, 512MBDave CheneyGOARM=5
linux-arm-cheney-imx6Solidrun Cubox-i, quad core Cortex-A9 ~ 1Ghz, 2Gb ramDave CheneyRuns arch linux, iMX6 boards need 3.10.x or above to pass the build reliably
linux-ppc64KVM instance on physical 8-core POWER7 pSeries. Chip rev: 2.1 (pvr 004b 0201)bradfitz, rsc
nacl-armsamsung chromebookrscrunning chrubuntu
nacl-arm-cheneysame builder as linux-arm-cheney-imx6Dave Cheney
netbsd-386-minuxKVMShenghou Ma
netbsd-amd64-bsiegertEC2 m1.small VMBenny Siegerton Brad's work EC2 account
plan9-386-cnielsenIntel Core 2 Quad Q8200 2.33 GHz, 6GBDavid du ColombierPlan 9 from Bell Labs, updated nightly
plan9-amd64-aramVMNick Owensruns 9front
solaris-amd64-smartosE5-1650 Xeon, 6C/12TDaniel Malonruns illumos (smartos zone); dfc, aram have full access
solaris-amd64-solaris11VMDave Cheneyruns Solaris 11

Builder Requirements

  • internet connection (at least be able to access Google and http://build.golang.org)
  • preferably with two or more (V)CPUs, as at least one test (sync/atomic requires runtime.NumCPU() > 1 to test more completely)
  • at least 512MiB of memory

Restrictions

  • The combination of Ubuntu 11.10 or 12.04 OMAP4 kernel and pandaboard (ES) have proven unstable as builders. See issue 4305. Make sure you have updated to the latest available 12.04.2 release.

How to set up a builder

  1. obtain a hash from Go team members, and put that in ~/.gobuildkey
  2. go get golang.org/x/build/cmd/builder
  3. builder YOUR_BUILDER_NAME

Special notes

  • Please make sure you‘ve installed root certificates and it’s accessible to Go programs. For example, on NetBSD, you will need to install security/mozilla-rootcerts.
  • If your builder runs Unix, please install perl, as tests for go.tools/cmd/vet need it.
  • Use screen(1) instead of tmux(1) to host the builder process, as the later interference with some of the os/signal tests.
  • Raise ulimits on Unix: thread count (-r), nofiles (-n, 1024 should be fine)