Zach Loafman 3458246c10 Publish a gs://kubernetes-release/release/latest.txt when we publish a build ...

Adds a kube::release::gcs::publish_latest_official that checks the
current contents of this file in GCS, verifies that we're pushing a
newer build, and updates it if so. (i.e. it handles the case of
pushing a 0.13.1 and then later pushing a 0.12.3.) This follows the
pattern of the ci/ build, which Jenkins just updates unconditionally.

I already updated the file for 0.13.1. After this we can update the
get-k8s script, so we don't have to keep updating it.

2015-03-17 13:53:05 -07:00

31 KiB

Raw Blame History

View Raw