builders: run builds in VMs in addition to containers #9492
Labels
Milestone
Comments
|
What about NetBSD? For ARM builders, I suggest we still use real hardware, because qemu system |
|
Yes, NetBSD, Solaris, etc. I just didn't list them all. For ARM, let's move discussion to #8647 |
|
It's starting to work ... Coordinator showing it's watching a buildlet on a VM it started: And the VM for just that one build: |
bradfitz
added a commit
to golang/tools
that referenced
this issue
Jan 5, 2015
Currently this is running an OpenBSD amd64 builder, but other operating systems are now easy. Updates golang/go#8642 Updates golang/go#9492 Change-Id: I4e1026c49ee4d253dfcf78c7606767294784f02e Reviewed-on: https://go-review.googlesource.com/2264 Reviewed-by: Andrew Gerrand <[email protected]>
bradfitz
added a commit
to golang/tools
that referenced
this issue
Jan 5, 2015
This uses the new JSON interface to the build dashboard (from golang.org/cl/2290) to find all work, and re-enables the OpenBSD builder[*], and can do multiple things at a time. Andrew and I just watched it fire up 8 OpenBSD VMs at once to catch up. [*] The OpenBSD builder was disabled because it would only report results for the main repo, not subrepos, and the old build.golang.org/todo interface didn't understand that was possible. Now the steps are considered separate. Update golang/go#8642 (OpenBSD) Update golang/go#9492 (builds in VMs) Change-Id: Ic6c2f73ee3da218dd54ef1a33f3afc97046ea3cc Reviewed-on: https://go-review.googlesource.com/2282 Reviewed-by: Andrew Gerrand <[email protected]>
|
NetBSD CL at https://go-review.googlesource.com/2612 |
bradfitz
added a commit
to golang/build
that referenced
this issue
Jan 21, 2015
Currently this is running an OpenBSD amd64 builder, but other operating systems are now easy. Updates golang/go#8642 Updates golang/go#9492 Change-Id: I4e1026c49ee4d253dfcf78c7606767294784f02e Reviewed-on: https://go-review.googlesource.com/2264 Reviewed-by: Andrew Gerrand <[email protected]>
bradfitz
added a commit
to golang/build
that referenced
this issue
Jan 21, 2015
This uses the new JSON interface to the build dashboard (from golang.org/cl/2290) to find all work, and re-enables the OpenBSD builder[*], and can do multiple things at a time. Andrew and I just watched it fire up 8 OpenBSD VMs at once to catch up. [*] The OpenBSD builder was disabled because it would only report results for the main repo, not subrepos, and the old build.golang.org/todo interface didn't understand that was possible. Now the steps are considered separate. Update golang/go#8642 (OpenBSD) Update golang/go#9492 (builds in VMs) Change-Id: Ic6c2f73ee3da218dd54ef1a33f3afc97046ea3cc Reviewed-on: https://go-review.googlesource.com/2282 Reviewed-by: Andrew Gerrand <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This bug is about the non-Linux (but still x86) part of http://golang.org/s/builderplan
The current build coordinator (x/tools/dashboard/coordinator) only runs builds in Docker containers. These are what https://github.com/golang/go/wiki/DashboardBuilders calls the "New-style" builders.
They're only Linux configs, though.
To run non-Linux OSes, we want to run VMs as well. This bug is about adding support to run builds in VMs on GCE (so x86 only)
The first part was recently done in https://go-review.googlesource.com/#/c/2180/ which added the buildlet. The buildlet runs on each VM (Windows, Plan 9, Open BSD, etc) and provides remote command execution and file extraction over HTTP. This is the interface that the coordinator will then use instead of docker for VM-based builds.
Specific bugs have been filed for each operating system moving to this new scheme:
FreeBSD is #8639
OpenBSD is #8642 (furthest along)
Windows is #8640
Plan 9 is #9491
The text was updated successfully, but these errors were encountered: