mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-07-28 22:17:14 +00:00
Merge pull request #18030 from ihmccreery/auto-config-upgrades-master
Configure gke-upgrade jobs from 1.0 and 1.1 to master on master
This commit is contained in:
commit
dd734ca1b8
@ -827,125 +827,40 @@ case ${JOB_NAME} in
|
||||
)"}
|
||||
;;
|
||||
|
||||
# kubernetes-upgrade-gke-1.0-current-release
|
||||
# kubernetes-upgrade-gke-1.0-master
|
||||
#
|
||||
# This suite:
|
||||
# Test upgrades from the latest release-1.0 build to the latest master build.
|
||||
#
|
||||
# 1. launches a cluster at ci/latest-1.0,
|
||||
# 2. upgrades the master to CURRENT_RELEASE_PUBLISHED_VERSION
|
||||
# 3. runs ci/latest-1.0 e2es,
|
||||
# 4. upgrades the rest of the cluster,
|
||||
# 5. runs ci/latest-1.0 e2es again, then
|
||||
# 6. runs CURRENT_RELEASE_PUBLISHED_VERSION e2es and tears down the cluster.
|
||||
# Configurations for step1, step3, and step5 live in the release-1.0 branch.
|
||||
|
||||
kubernetes-upgrade-1.0-current-release-gke-step1-deploy)
|
||||
: ${DOGFOOD_GCLOUD:="true"}
|
||||
: ${GKE_API_ENDPOINT:="https://test-container.sandbox.googleapis.com/"}
|
||||
: ${E2E_CLUSTER_NAME:="gke-upgrade-1-0"}
|
||||
: ${E2E_NETWORK:="gke-upgrade-1-0"}
|
||||
: ${JENKINS_PUBLISHED_VERSION:="ci/latest-1.0"}
|
||||
: ${E2E_SET_CLUSTER_API_VERSION:=y}
|
||||
: ${PROJECT:="kubernetes-jenkins-gke-upgrade"}
|
||||
: ${E2E_UP:="true"}
|
||||
: ${E2E_TEST:="false"}
|
||||
: ${E2E_DOWN:="false"}
|
||||
kubernetes-upgrade-gke-1.0-master-step2-upgrade-master)
|
||||
configure_upgrade_step 'configured-in-release-1.0' 'ci/latest' 'upgrade-gke-1-0-master' 'kubernetes-jenkins-gke-upgrade'
|
||||
;;
|
||||
|
||||
kubernetes-upgrade-1.0-current-release-gke-step2-upgrade-master)
|
||||
: ${DOGFOOD_GCLOUD:="true"}
|
||||
: ${GKE_API_ENDPOINT:="https://test-container.sandbox.googleapis.com/"}
|
||||
: ${E2E_CLUSTER_NAME:="gke-upgrade-1-0"}
|
||||
: ${E2E_NETWORK:="gke-upgrade-1-0"}
|
||||
: ${E2E_OPT:="--check_version_skew=false"}
|
||||
# Use upgrade logic of version we're upgrading to.
|
||||
: ${JENKINS_PUBLISHED_VERSION:="${CURRENT_RELEASE_PUBLISHED_VERSION}"}
|
||||
: ${JENKINS_FORCE_GET_TARS:=y}
|
||||
: ${PROJECT:="kubernetes-jenkins-gke-upgrade"}
|
||||
: ${E2E_UP:="false"}
|
||||
: ${E2E_TEST:="true"}
|
||||
: ${E2E_DOWN:="false"}
|
||||
: ${GINKGO_TEST_ARGS:="--ginkgo.focus=Cluster\sUpgrade.*upgrade-master --upgrade-target=${CURRENT_RELEASE_PUBLISHED_VERSION}"}
|
||||
kubernetes-upgrade-gke-1.0-master-step4-upgrade-cluster)
|
||||
configure_upgrade_step 'configured-in-release-1.0' 'ci/latest' 'upgrade-gke-1-0-master' 'kubernetes-jenkins-gke-upgrade'
|
||||
;;
|
||||
|
||||
kubernetes-upgrade-1.0-current-release-gke-step3-e2e-old)
|
||||
: ${DOGFOOD_GCLOUD:="true"}
|
||||
: ${GKE_API_ENDPOINT:="https://test-container.sandbox.googleapis.com/"}
|
||||
: ${E2E_CLUSTER_NAME:="gke-upgrade-1-0"}
|
||||
: ${E2E_NETWORK:="gke-upgrade-1-0"}
|
||||
: ${E2E_OPT:="--check_version_skew=false"}
|
||||
: ${JENKINS_FORCE_GET_TARS:=y}
|
||||
# Run old e2es
|
||||
: ${JENKINS_PUBLISHED_VERSION:="ci/latest-1.0"}
|
||||
: ${PROJECT:="kubernetes-jenkins-gke-upgrade"}
|
||||
: ${E2E_UP:="false"}
|
||||
: ${E2E_TEST:="true"}
|
||||
: ${E2E_DOWN:="false"}
|
||||
: ${GINKGO_TEST_ARGS:="--ginkgo.skip=$(join_regex_allow_empty \
|
||||
${GKE_DEFAULT_SKIP_TESTS[@]:+${GKE_DEFAULT_SKIP_TESTS[@]}} \
|
||||
${GCE_DEFAULT_SKIP_TESTS[@]:+${GCE_DEFAULT_SKIP_TESTS[@]}} \
|
||||
${GCE_FLAKY_TESTS[@]:+${GCE_FLAKY_TESTS[@]}} \
|
||||
${GKE_FLAKY_TESTS[@]:+${GKE_FLAKY_TESTS[@]}} \
|
||||
)"}
|
||||
kubernetes-upgrade-gke-1.0-master-step6-e2e-new)
|
||||
configure_upgrade_step 'configured-in-release-1.0' 'ci/latest' 'upgrade-gke-1-0-master' 'kubernetes-jenkins-gke-upgrade'
|
||||
;;
|
||||
|
||||
kubernetes-upgrade-1.0-current-release-gke-step4-upgrade-cluster)
|
||||
: ${DOGFOOD_GCLOUD:="true"}
|
||||
: ${GKE_API_ENDPOINT:="https://test-container.sandbox.googleapis.com/"}
|
||||
: ${E2E_CLUSTER_NAME:="gke-upgrade-1-0"}
|
||||
: ${E2E_NETWORK:="gke-upgrade-1-0"}
|
||||
: ${E2E_OPT:="--check_version_skew=false"}
|
||||
# Use upgrade logic of version we're upgrading to.
|
||||
: ${JENKINS_PUBLISHED_VERSION:="${CURRENT_RELEASE_PUBLISHED_VERSION}"}
|
||||
: ${JENKINS_FORCE_GET_TARS:=y}
|
||||
: ${PROJECT:="kubernetes-jenkins-gke-upgrade"}
|
||||
: ${E2E_UP:="false"}
|
||||
: ${E2E_TEST:="true"}
|
||||
: ${E2E_DOWN:="false"}
|
||||
: ${GINKGO_TEST_ARGS:="--ginkgo.focus=Cluster\sUpgrade.*upgrade-cluster --upgrade-target=${CURRENT_RELEASE_PUBLISHED_VERSION}"}
|
||||
# kubernetes-upgrade-gke-1.1-master
|
||||
#
|
||||
# Test upgrades from the latest release-1.1 build to the latest master build.
|
||||
#
|
||||
# Configurations for step1, step3, and step5 live in the release-1.1 branch.
|
||||
|
||||
kubernetes-upgrade-gke-1.1-master-step2-upgrade-master)
|
||||
configure_upgrade_step 'configured-in-release-1.1' 'ci/latest' 'upgrade-gke-1-1-master' 'kubernetes-jenkins-gke-upgrade'
|
||||
;;
|
||||
|
||||
kubernetes-upgrade-1.0-current-release-gke-step5-e2e-old)
|
||||
: ${DOGFOOD_GCLOUD:="true"}
|
||||
: ${GKE_API_ENDPOINT:="https://test-container.sandbox.googleapis.com/"}
|
||||
: ${E2E_CLUSTER_NAME:="gke-upgrade-1-0"}
|
||||
: ${E2E_NETWORK:="gke-upgrade-1-0"}
|
||||
: ${E2E_OPT:="--check_version_skew=false"}
|
||||
: ${JENKINS_FORCE_GET_TARS:=y}
|
||||
# Run old e2es
|
||||
: ${JENKINS_PUBLISHED_VERSION:="ci/latest-1.0"}
|
||||
: ${PROJECT:="kubernetes-jenkins-gke-upgrade"}
|
||||
: ${E2E_UP:="false"}
|
||||
: ${E2E_TEST:="true"}
|
||||
: ${E2E_DOWN:="false"}
|
||||
: ${GINKGO_TEST_ARGS:="--ginkgo.skip=$(join_regex_allow_empty \
|
||||
${GKE_DEFAULT_SKIP_TESTS[@]:+${GKE_DEFAULT_SKIP_TESTS[@]}} \
|
||||
${GCE_DEFAULT_SKIP_TESTS[@]:+${GCE_DEFAULT_SKIP_TESTS[@]}} \
|
||||
${GCE_FLAKY_TESTS[@]:+${GCE_FLAKY_TESTS[@]}} \
|
||||
${GKE_FLAKY_TESTS[@]:+${GKE_FLAKY_TESTS[@]}} \
|
||||
)"}
|
||||
kubernetes-upgrade-gke-1.1-master-step4-upgrade-cluster)
|
||||
configure_upgrade_step 'configured-in-release-1.1' 'ci/latest' 'upgrade-gke-1-1-master' 'kubernetes-jenkins-gke-upgrade'
|
||||
;;
|
||||
|
||||
kubernetes-upgrade-1.0-current-release-gke-step6-e2e-new)
|
||||
: ${DOGFOOD_GCLOUD:="true"}
|
||||
: ${GKE_API_ENDPOINT:="https://test-container.sandbox.googleapis.com/"}
|
||||
: ${E2E_CLUSTER_NAME:="gke-upgrade-1-0"}
|
||||
: ${E2E_NETWORK:="gke-upgrade-1-0"}
|
||||
# TODO(15011): these really shouldn't be (very) version skewed, but because
|
||||
# we have to get CURRENT_RELEASE_PUBLISHED_VERSION again, it could get slightly out of whack.
|
||||
: ${E2E_OPT:="--check_version_skew=false"}
|
||||
: ${JENKINS_FORCE_GET_TARS:=y}
|
||||
: ${JENKINS_PUBLISHED_VERSION:="${CURRENT_RELEASE_PUBLISHED_VERSION}"}
|
||||
: ${PROJECT:="kubernetes-jenkins-gke-upgrade"}
|
||||
: ${E2E_UP:="false"}
|
||||
: ${E2E_TEST:="true"}
|
||||
: ${E2E_DOWN:="true"}
|
||||
: ${GINKGO_TEST_ARGS:="--ginkgo.skip=$(join_regex_allow_empty \
|
||||
${GKE_DEFAULT_SKIP_TESTS[@]:+${GKE_DEFAULT_SKIP_TESTS[@]}} \
|
||||
${GCE_DEFAULT_SKIP_TESTS[@]:+${GCE_DEFAULT_SKIP_TESTS[@]}} \
|
||||
${GCE_FLAKY_TESTS[@]:+${GCE_FLAKY_TESTS[@]}} \
|
||||
${GKE_FLAKY_TESTS[@]:+${GKE_FLAKY_TESTS[@]}} \
|
||||
${GCE_SLOW_TESTS[@]:+${GCE_SLOW_TESTS[@]}} \
|
||||
)"}
|
||||
kubernetes-upgrade-gke-1.1-master-step6-e2e-new)
|
||||
configure_upgrade_step 'configured-in-release-1.1' 'ci/latest' 'upgrade-gke-1-1-master' 'kubernetes-jenkins-gke-upgrade'
|
||||
;;
|
||||
|
||||
# kubernetes-upgrade-gce
|
||||
@ -1068,7 +983,7 @@ case ${JOB_NAME} in
|
||||
# 5. runs ci/latest-1.0 e2es again, then
|
||||
# 6. runs CURRENT_RELEASE_PUBLISHED_VERSION e2es and tears down the cluster.
|
||||
|
||||
kubernetes-upgrade-1.0-current-release-gce-step1-deploy)
|
||||
kubernetes-upgrade-1.0-current-release-gce-step1-deploy)
|
||||
: ${E2E_CLUSTER_NAME:="gce-upgrade-1-0"}
|
||||
: ${E2E_NETWORK:="gce-upgrade-1-0"}
|
||||
: ${JENKINS_PUBLISHED_VERSION:="ci/latest-1.0"}
|
||||
|
Loading…
Reference in New Issue
Block a user