build/buildlet
Alexander Rakoczy 22bdacadd1 cmd/coordinator,buildlet: keep active GCE SSH sessions alive
This CL skips deleting active remote buildlets.

The coordinator has multiple ways of tracking stale buildlets. For our
GCE buildlets, we periodically delete old VMs after their expiration
time, typically 45 minutes after their creation. The expiration tracking
in coordinator/gce.go does not account for remote buildlets, which are
buildlets created by users or cmd/release. Remote buildlets have their
own staleness checks and cleanup process, so we should skip the GCE
specific cleanup logic for them.

This adds an additional field to the buildlet Client in order to
correlate a GCE VM with a buildlet.

Updates golang/go#37001

Change-Id: Ib0acdf79c4dfbee6e0061c513f98b749d4b9cc64
Reviewed-on: https://go-review.googlesource.com/c/build/+/217722
Run-TryBot: Alexander Rakoczy <alex@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-02-06 15:35:01 +00:00
..
README.md all: add README.md files where missing, and tool to keep them updated 2017-08-02 22:17:52 +00:00
buildletclient.go cmd/coordinator,buildlet: keep active GCE SSH sessions alive 2020-02-06 15:35:01 +00:00
gce.go buildlet: use a dedicated service account on GCE 2019-12-13 17:33:05 +00:00
keypair.go buildlet: set TCP keep-alive timeouts, avoid fd leaks 2015-02-03 11:38:45 +00:00
kube.go all: remove use old, overloaded of IN_KUBERNETES 2019-10-17 19:02:58 +00:00
remote.go cmd/coordinator, cmd/gomote: show periodic status updates to stderr 2019-11-20 22:32:37 +00:00

README.md

GoDoc

golang.org/x/build/buildlet

Package buildlet contains client tools for working with a buildlet server.