github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-17 15:50:10 +00:00
Code Issues Projects Releases Wiki Activity

Move gke ingress tests into a different project.

Browse Source
This commit is contained in:
Prashanth Balasubramanian 2016-03-01 19:03:17 -08:00
parent 577eb94c68
commit 67e1ddddfb
1 changed files with 1 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
hack/jenkins/job-configs/kubernetes-e2e.yaml
View File

@ -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.'