Merge pull request #29877 from spxtr/gke-build

Automatic merge from submit-queue GKE test-build-release: Actually do the build. Multiple devs (myself included!) have experienced frustration with the fact that if `KUBERNETES_PROVIDER=gke` then `hack/e2e.go --build` doesn't actually do a build. Are we actually relying on this behavior anywhere?

Merge pull request #29877 from spxtr/gke-build
fa5f3b81 · Kubernetes Submit Queue · GitHub · f2a9ba23 · 95ea9586 · fa5f3b81
Commit fa5f3b81 authored Aug 02, 2016 by Kubernetes Submit Queue Committed by GitHub Aug 02, 2016
Show whitespace changes
Inline Side-by-side

Showing with 4 additions and 2 deletions

util.sh cluster/gke/util.sh +4 -2

No files found.
--- a/cluster/gke/util.sh
+++ b/cluster/gke/util.sh
@@ -63,10 +63,12 @@ function detect-project() {
 }
 # Execute prior to running tests to build a release if required for env.
+#
+# Assumed Vars:
+#   KUBE_ROOT
 function test-build-release() {
  echo "... in gke:test-build-release()" >&2
-  echo "... We currently use the Kubernetes version that GKE supports,"
+  "${KUBE_ROOT}/build/release.sh"
-  echo "... not bleeding-edge builds."
 }
 # Verify needed binaries exist.