Upgrades and upgrade tests take versions of the form release/stable instead of stable_release:

- Refactor common and gce/upgrade.sh to use arbitrary published releases
- Update hack/get-build to use cluster/common code
- Use hack/get-build.sh in cluster upgrade test logic
This commit is contained in:
Isaac Hollander McCreery
2015-10-12 16:11:12 -07:00
parent e929977ff3
commit 60c316b54a
8 changed files with 120 additions and 141 deletions

View File

@@ -35,17 +35,27 @@ Documentation for other releases can be found at
You can use [hack/get-build.sh](http://releases.k8s.io/HEAD/hack/get-build.sh) to or use as a reference on how to get the most recent builds with curl. With `get-build.sh` you can grab the most recent stable build, the most recent release candidate, or the most recent build to pass our ci and gce e2e tests (essentially a nightly build).
```console
usage:
./hack/get-build.sh [stable|release|latest|latest-green]
Run `./hack/get-build.sh -h` for its usage.
stable: latest stable version
release: latest release candidate
latest: latest ci build
latest-green: latest ci build to pass gce e2e
For example, to get a build at a specific version (v1.0.2):
```console
./hack/get-build.sh v1.0.2
```
You can also use the gsutil tool to explore the Google Cloud Storage release bucket. Here are some examples:
Alternatively, to get the latest stable release:
```console
./hack/get-build.sh release/stable
```
Finally, you can just print the latest or stable version:
```console
./hack/get-build.sh -v ci/latest
```
You can also use the gsutil tool to explore the Google Cloud Storage release buckets. Here are some examples:
```sh
gsutil cat gs://kubernetes-release/ci/latest.txt # output the latest ci version number