github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-29 06:27:05 +00:00
Code Issues Projects Releases Wiki Activity

Don't check for version skew when testing an upgraded-to-CI cluster

Browse Source
This commit is contained in:
Isaac Hollander McCreery 2015-10-02 11:53:16 -07:00
parent 6b7fe871b2
commit cedc07568b
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
hack/jenkins/e2e.sh
View File

@ -558,6 +558,9 @@ case ${JOB_NAME} in
: ${GKE_API_ENDPOINT:="https://test-container.sandbox.googleapis.com/"} : ${GKE_API_ENDPOINT:="https://test-container.sandbox.googleapis.com/"}
: ${E2E_CLUSTER_NAME:="gke-upgrade"} : ${E2E_CLUSTER_NAME:="gke-upgrade"}
: ${E2E_NETWORK:="gke-upgrade"} : ${E2E_NETWORK:="gke-upgrade"}
# TODO(15011): these really shouldn't be (very) version skewed, but because
# we have to rebuild, it could get slightly out of whack.
: ${E2E_OPT:="--check_version_skew=false"}
: ${JENKINS_FORCE_GET_TARS:=y} : ${JENKINS_FORCE_GET_TARS:=y}
# Run ci (new) e2es, not release (old) # Run ci (new) e2es, not release (old)
: ${JENKINS_USE_RELEASE_TARS:=n} : ${JENKINS_USE_RELEASE_TARS:=n}