зеркало из https://github.com/golang/build.git
22bdacadd1
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> |
||
---|---|---|
.. | ||
README.md | ||
buildletclient.go | ||
gce.go | ||
keypair.go | ||
kube.go | ||
remote.go |