From 804903f32022380ea89b06ea735d93c05e7a1426 Mon Sep 17 00:00:00 2001 From: Prashanth Balasubramanian Date: Fri, 5 Feb 2016 17:27:27 -0800 Subject: [PATCH] Move ingress tests to a different project. --- hack/jenkins/job-configs/kubernetes-e2e.yaml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/hack/jenkins/job-configs/kubernetes-e2e.yaml b/hack/jenkins/job-configs/kubernetes-e2e.yaml index 0a3deb9f611..fd9d5bf0e2e 100644 --- a/hack/jenkins/job-configs/kubernetes-e2e.yaml +++ b/hack/jenkins/job-configs/kubernetes-e2e.yaml @@ -363,7 +363,7 @@ # 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-flannel" + export PROJECT="kubernetes-ingress" - 'gce-ingress': description: 'Run [Feature:Ingress] tests on GCE.' timeout: 90 @@ -377,10 +377,12 @@ # 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-flannel" + 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.' - timeout: 90 + # We don't really care to enforce a timeout for flannel tests. Any performance issues will show up in the other GCE builders. + # This suite is to continuously check that flannel + Kubernetes works. + timeout: 120 emails: 'beeps@google.com' test-owner: 'beeps' provider-env: '{gce-provider-env}'