Relui replaced release since Go 1.18 or so. We kept it around a bit
longer while there were remaining Go+BoringCrypto releases that still
used the release command. Those are no more, so to avoid confusion,
remove cmd/release code given it's no longer maintained or supported.
Updates golang/go#40279.
Updates golang/go#58659.
Fixesgolang/go#45893.
Change-Id: Id0d641bee49c9584c52e5616322f0656b89cd851
Reviewed-on: https://go-review.googlesource.com/c/build/+/470755
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Heschi Kreinick <heschi@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Carlos Amedee <carlos@golang.org>
Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
The staging section was commented out because that environment is not
supported. It's still visible when viewing the .md file in its raw form
and has proven to cause confusion. Since we can easily get it back from
history if/when it becomes needed again, hide it better by deleting it.
Change-Id: Ifb227d3238d88a9d1c6be58dd95e2b7829b85315
Reviewed-on: https://go-review.googlesource.com/c/build/+/463575
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Matthew Dempsky <mdempsky@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
It seems easy for someone new to x/build services and looking up how to
deploy one for the first time to mistake the "deploying for the first
time" section as being applicable to them. In reality, it shows commands
that are only relevant when creating new services, which we do rarely.
There are many useful but less-frequently used kubectl commands (apply,
create, etc.) that are already documented elsewhere, and we benefit
little from repeating them here. Remove this section to reduce possible
confusion and to make the deployment document shorter.
(If we want to add these back in the future, they should probably go
under a clear "advanced / infrequent use" section or a separate file.)
Change-Id: I930f463e5800f41f1e815c791b6e48153760a9d9
Reviewed-on: https://go-review.googlesource.com/c/build/+/418534
Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Michael Knyszek <mknyszek@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
This change moves the devapp deployment documentation into the doc
directory because it's common to all services that run in the GKE
cluster.
It also restructures that documentation just a little to alleviate some
confusion (i.e. make push-prod is not necessary if using make
deploy-prod).
Then, it updates all the relevant services' documentation to refer to
that shared document.
Also, it touch up a couple of the services' READMEs, like gopherbot and
pubsubhelper.
Change-Id: I3774385f1d0ba9e9886ece8462294c1f28e8bd17
Reviewed-on: https://go-review.googlesource.com/c/build/+/416220
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Since farmer.golang.org has a valid certificate in production now, we
should use that certificate for retrieving data.
Change-Id: I3685d84953ea11e6ac09b4692fa27c73538a565c
Reviewed-on: https://go-review.googlesource.com/39290
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
This creates a mechanism for clients (such as cmd/release and
cmd/gomote) to obtain buildlets via the coordinator. Previously
cmd/release and cmd/gomote could only create GCE VMs themselves, and
required the GCE project's credentials. In addition to the awkwardness
of needing to hand out the GCE credentials, it also meant ARM and
Darwin buildlets (which use the reverse buildlet pool) weren't usable.
Instead, this creates a new auth mechanism where the coordinator is
contacted over TLS with key pinning (the CA system isn't used) in the
same way that the reverse builders already dialed into the
coordinator, and then a "user build type" and hash are sent as the
username and password. The same master key is used to sign user
builder keys, and they always start with "user-". (which isn't a GOOS).
Then the coordinator provides an API to create and list buildlets.
They auto-expire after a duration and are auto-renewed upon use.
The buildlet library (as used by cmd/release etc) then proxies HTTP
requests via the coordinator to the backend buildlet.
See doc/remote-buildlet.txt for protocol details.
Change-Id: I12e27eae788fdd91927cb182b950893dc759f8e9
Reviewed-on: https://go-review.googlesource.com/11901
Reviewed-by: Andrew Gerrand <adg@golang.org>
Dmitri Shuralyov
Michael Anthony Knyszek
Kevin Burke
Brad Fitzpatrick