From e055ee0b716e87740688e8c2051b1d92401d91ef Mon Sep 17 00:00:00 2001 From: Zach Loafman Date: Wed, 22 Apr 2015 10:06:01 -0700 Subject: [PATCH] Use KUBE_SKIP_UPDATE in Jenkins After #7146, we need to protect Jenkins from the internal gcloud bug (again). --- hack/jenkins/e2e.sh | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/hack/jenkins/e2e.sh b/hack/jenkins/e2e.sh index 32970ddab04..785f6c9e69f 100755 --- a/hack/jenkins/e2e.sh +++ b/hack/jenkins/e2e.sh @@ -102,6 +102,10 @@ else exit 1 fi + # Tell kube-up.sh to skip the update, it doesn't lock. An internal + # gcloud bug can cause racing component updates to stomp on each + # other. + export KUBE_SKIP_UPDATE=y sudo flock -x -n /var/run/lock/gcloud-components.lock -c "gcloud components update -q" || true # The "ci" bucket is for builds like "v0.15.0-468-gfa648c1"