Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add feature: ingress to the release 1.2 suite #23203

Merged
merged 1 commit into from
Mar 19, 2016
Merged

Add feature: ingress to the release 1.2 suite #23203

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
26 changes: 25 additions & 1 deletion hack/jenkins/job-configs/kubernetes-jenkins/kubernetes-e2e.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -255,6 +255,16 @@
export GINKGO_TEST_ARGS="--ginkgo.focus=\[Serial\]|\[Disruptive\] \
--ginkgo.skip=\[Flaky\]|\[Feature:.+\]"
export PROJECT="k8s-jkns-e2e-gce-serial-1-2"
- 'gce-ingress-release-1.2':
description: 'Run [Feature:Ingress] tests on GCE on the release-1.2 branch.'
timeout: 90
emails: 'beeps@google.com'
test-owner: 'beeps'
job-env: |
export GINKGO_TEST_ARGS="--ginkgo.focus=\[Feature:Ingress\]"
export PROJECT="kubernetes-ingress"
# TODO: Enable this when we've split 1.2 tests into another project.
export FAIL_ON_GCP_RESOURCE_LEAK="false"
- 'gce-scalability-release-1.2':
timeout: 120
description: 'Run scalability E2E tests on GCE from the release-1.2 branch.'
Expand Down Expand Up @@ -285,7 +295,7 @@
export TEST_CLUSTER_DELETE_COLLECTION_WORKERS="--delete-collection-workers=16"
jobs:
- 'kubernetes-e2e-{suffix}'

- project:
name: kubernetes-e2e-gke-1-2
trigger-job: 'kubernetes-build-1.2'
Expand Down Expand Up @@ -316,6 +326,16 @@
export GINKGO_TEST_ARGS="--ginkgo.focus=\[Slow\] \
--ginkgo.skip=\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]"
export GINKGO_PARALLEL="y"
- 'gke-ingress-release-1.2':
description: 'Run [Feature:Ingress] tests on GKE on the release-1.2 branch.'
timeout: 90
emails: 'beeps@google.com'
test-owner: 'beeps'
job-env: |
export GINKGO_TEST_ARGS="--ginkgo.focus=\[Feature:Ingress\]"
export PROJECT="kubernetes-gke-ingress"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the right project?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah it has quota. I'd create a new one but then have to wait till quota is granted etc, so I just put the todo and FAIL_ON_GCP_RESOURCE_LEAK=false (the test will fail if there's a leak based on internal checks anyway)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also this project has the gke side flag we need to flip with an internal cl each time a new e2e gke project is created

# TODO: Enable this when we've split 1.2 tests into another project.
export FAIL_ON_GCP_RESOURCE_LEAK="false"
jobs:
- 'kubernetes-e2e-{suffix}'

Expand Down Expand Up @@ -462,6 +482,8 @@
job-env: |
export GINKGO_TEST_ARGS="--ginkgo.focus=\[Feature:Ingress\]"
export PROJECT="kubernetes-gke-ingress"
# TODO: Enable this when we've split 1.2 tests into another project.
export FAIL_ON_GCP_RESOURCE_LEAK="false"
- 'gce-ingress':
description: 'Run [Feature:Ingress] tests on GCE.'
timeout: 90
Expand All @@ -471,6 +493,8 @@
job-env: |
export GINKGO_TEST_ARGS="--ginkgo.focus=\[Feature:Ingress\]"
export PROJECT="kubernetes-ingress"
# TODO: Enable this when we've split 1.2 tests into another project.
export FAIL_ON_GCP_RESOURCE_LEAK="false"
- '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.'
# We don't really care to enforce a timeout for flannel tests. Any performance issues will show up in the other GCE builders.
Expand Down