Split gke-gci-new-gci-master-upgrade-cluster-new into parallel and serial jobs
By splitting into a parallel job and a serial job, we can put the Slow
tests in the parallel job (only), and still achieve coverage of the
Serial and Disruptive tests in the serial job (only).
Issue
@@ -2292,6 +2292,8 @@ test_groups:
gcs_prefix: kubernetes-jenkins/logs/ci-kubernetes-e2e-gke-gci-master-gci-new-downgrade-cluster-parallel
- name: ci-kubernetes-e2e-gke-gci-new-gci-master-upgrade-cluster-new
gcs_prefix: kubernetes-jenkins/logs/ci-kubernetes-e2e-gke-gci-new-gci-master-upgrade-cluster-new
+- name: ci-kubernetes-e2e-gke-gci-new-gci-master-upgrade-cluster-new-parallel
+ gcs_prefix: kubernetes-jenkins/logs/ci-kubernetes-e2e-gke-gci-new-gci-master-upgrade-cluster-new-parallel
- name: ci-kubernetes-multicluster-ingress-test
gcs_prefix: kubernetes-jenkins/logs/ci-kubernetes-multicluster-ingress-test
- name: kubeflow-periodic-release-branch
@@ -4544,7 +4546,10 @@ dashboards:
description: Downgrade master and node, in gke(gci), from master to 1.10, run parallel tests only
- name: gke-gci-new-gci-master-upgrade-cluster-new
test_group_name: ci-kubernetes-e2e-gke-gci-new-gci-master-upgrade-cluster-new
- description: Upgrade master and node, in gke(gci), from 1.10 to master, and run skewed e2e tests
+ description: Upgrade master and node, in gke(gci), from 1.10 to master, and run skewed e2e tests; skipping slow tests as we run serially
+ - name: gke-gci-new-gci-master-upgrade-cluster-new-parallel
+ test_group_name: ci-kubernetes-e2e-gke-gci-new-gci-master-upgrade-cluster-new-parallel
+ description: Upgrade master and node, in gke(gci), from 1.10 to master, and run skewed e2e tests; skipping serial and disruptive tests as we run in parallel
# These are the master *blocking* tests. These provide a valid binary signal
# to gate releases (alpha, beta, official).
