diff --git a/hack/jenkins/job-configs/kubernetes-jenkins/kubernetes-e2e.yaml b/hack/jenkins/job-configs/kubernetes-jenkins/kubernetes-e2e.yaml index 2a9a34c8d93..1bfc520d41d 100644 --- a/hack/jenkins/job-configs/kubernetes-jenkins/kubernetes-e2e.yaml +++ b/hack/jenkins/job-configs/kubernetes-jenkins/kubernetes-e2e.yaml @@ -464,9 +464,6 @@ - 'gce-release-1.1': timeout: 175 description: 'Run E2E tests on GCE from the current release branch.' - - 'gce-disruptive-1.1': - timeout: 180 - description: 'Run disruptive E2E tests on GCE from the current release branch.' jobs: - 'kubernetes-e2e-{suffix}' diff --git a/hack/jenkins/job-configs/kubernetes-jenkins/kubernetes-soak.yaml b/hack/jenkins/job-configs/kubernetes-jenkins/kubernetes-soak.yaml index c709dc95898..6b8b2682dea 100644 --- a/hack/jenkins/job-configs/kubernetes-jenkins/kubernetes-soak.yaml +++ b/hack/jenkins/job-configs/kubernetes-jenkins/kubernetes-soak.yaml @@ -129,25 +129,6 @@ job-env: | export PROJECT="k8s-jkns-gce-soak-1-2" export JENKINS_PUBLISHED_VERSION="ci/latest-1.2" - - 'gce-1.1': - deploy-description: | - Deploy Kubernetes to soak cluster using the latest successful - current release CI-produced Kubernetes build every week.
- If a kubernetes-soak-continuous-e2e-gce-1.1 build is running, - this deployment build will be blocked and remain in the queue - until the test run is complete.
- e2e-description: | - Assumes Kubernetes soak current-release cluster is already - deployed.
- If a kubernetes-soak-weekly-deploy-gce-1.1 build is enqueued, - builds will be blocked and remain in the queue until the - deployment is complete.
- branch: 'release-1.1' - runner: '{old-runner-1-1}' - post-env: '' - soak-deploy: '' - soak-continuous: '' - cron-string: 'H */6 * * *' - 'gke': deploy-description: | Deploy Kubernetes to a GKE soak cluster using the staging GKE