зеркало из https://github.com/golang/build.git
10d5d32f2c
Add the windows-arm64 builder to the dashboard and coordinator with a known issue until we can verify builds are succeeding regularly. Also, tweak the logic around validating ec2 configurations. The arm64 buildlet sets VMImage but not ContainerImage, unlike other ec2 buildlets. This should work for both. For golang/go#42604 Change-Id: I7176b8f6bba837830a0565e7713c9e9a0eb76e90 Reviewed-on: https://go-review.googlesource.com/c/build/+/322656 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> |
||
---|---|---|
.. | ||
README.md | ||
builders.go | ||
builders_test.go |
README.md
golang.org/x/build/dashboard
Package dashboard contains shared configuration and logic used by various pieces of the Go continuous build system.
Deploying
When adding or removing builders, or changing a builder's build policy
(which repos/branches get tested), you need to deploy the
x/build/cmd/coordinator
binary. Additionally, you usually want to
re-deploy the x/build/app/appengine
code to update
https://build.golang.org/. The latter is only for humans (forcing
columns to show up and adding the little black dots on cells that
aren't built), but doesn't affect what gets built.