From 67e1ddddfb2930e951977f17338f1d8c39ed29bd Mon Sep 17 00:00:00 2001 From: Prashanth Balasubramanian Date: Tue, 1 Mar 2016 19:03:17 -0800 Subject: [PATCH] Move gke ingress tests into a different project. --- hack/jenkins/job-configs/kubernetes-e2e.yaml | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/hack/jenkins/job-configs/kubernetes-e2e.yaml b/hack/jenkins/job-configs/kubernetes-e2e.yaml index 2492506ce4..19dc491da8 100644 --- a/hack/jenkins/job-configs/kubernetes-e2e.yaml +++ b/hack/jenkins/job-configs/kubernetes-e2e.yaml @@ -358,13 +358,8 @@ test-owner: 'beeps' provider-env: '{gke-provider-env}' job-env: | - # XXX Not a unique project - export E2E_NAME="e2e-gke-ingress" export GINKGO_TEST_ARGS="--ginkgo.focus=\[Feature:Ingress\]" - # TODO: Move this into a different project. Currently, since this test - # shares resources with various other networking tests, it's easier to - # zero in on the source of a leak if it's run in isolation. - export PROJECT="kubernetes-ingress" + export PROJECT="kubernetes-gke-ingress" - 'gce-ingress': description: 'Run [Feature:Ingress] tests on GCE.' timeout: 90 @@ -372,12 +367,7 @@ test-owner: 'beeps' provider-env: '{gce-provider-env}' job-env: | - # XXX Not a unique project - export E2E_NAME="e2e-ingress" export GINKGO_TEST_ARGS="--ginkgo.focus=\[Feature:Ingress\]" - # TODO: Move this into a different project. Currently, since this test - # shares resources with various other networking tests, so it's easier - # to zero in on the source of a leak if it's run in isolation. export PROJECT="kubernetes-ingress" - 'gce-flannel': description: 'Run E2E tests on GCE using Flannel and the latest successful build. This suite is quarantined in a dedicated project because Flannel integration is experimental.'