Migrate gke-trusty test jobs to 1.2 #23454
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -758,48 +758,88 @@ | |
| jobs: | ||
| - 'kubernetes-e2e-gce-trusty-{suffix}' | ||
|
|
||
| # Jobs that run e2e tests on GKE with Trusty as node image on the release-1.2 | ||
| # branch. Note that the variable "E2E_NAME" in all following jobs are set to | ||
| # have the "-trusty" suffix, which is required to start a GKE cluster with | ||
| # Trusty images. The variable "KUBE_OS_DISTRIBUTION" is set to "trusty" so that | ||
| # the OS dependendent test cases will use Trusty in their assertions. | ||
| - project: | ||
| name: kubernetes-e2e-gke-trusty | ||
| trigger-job: 'kubernetes-build-1.2' | ||
| test-owner: 'wonderfly@google.com' | ||
| provider-env: | | ||
| {gke-provider-env} | ||
| emails: 'wonderfly@google.com,qzheng@google.com' | ||
| suffix: | ||
| - 'gke-trusty-test': | ||
| description: 'Run E2E tests on GKE test endpoint.' | ||
| timeout: 480 | ||
| job-env: | | ||
| export PROJECT="kubekins-e2e-gke-trusty-test" | ||
| export CLOUDSDK_BUCKET="gs://cloud-sdk-testing/rc" | ||
| export JENKINS_USE_SERVER_VERSION="y" | ||
| export E2E_NAME="jkns-gke-e2e-test-trusty" | ||
|
There was a problem hiding this comment. Since each of these is running in a separate project, please don't use There was a problem hiding this comment. The default value of There was a problem hiding this comment. Please add an explanation comment. |
||
| export KUBE_OS_DISTRIBUTION="trusty" | ||
| - 'gke-trusty-subnet': | ||
| description: 'Run E2E tests on GKE test endpoint in a subnet.' | ||
| timeout: 480 | ||
| job-env: | | ||
| # Subnetwork "jkns-gke-e2e-subnet-trusty" is manually created - | ||
| # if deleted, it will need to be recreated via | ||
| # `gcloud alpha compute networks create jkns-gke-e2e-subnet-trusty --mode auto` | ||
| export PROJECT="k8s-e2e-gke-trusty-subnet" | ||
| export CLOUDSDK_BUCKET="gs://cloud-sdk-testing/rc" | ||
| export JENKINS_USE_SERVER_VERSION="y" | ||
| export E2E_NAME="jkns-gke-e2e-subnet-trusty" | ||
| export KUBE_OS_DISTRIBUTION="trusty" | ||
| - 'gke-trusty-staging': | ||
| description: 'Run E2E tests on GKE staging endpoint.' | ||
| timeout: 480 | ||
| job-env: | | ||
| export PROJECT="e2e-gke-trusty-staging" | ||
| export CLOUDSDK_BUCKET="gs://cloud-sdk-testing/rc" | ||
| export JENKINS_USE_SERVER_VERSION="y" | ||
| export CLOUDSDK_API_ENDPOINT_OVERRIDES_CONTAINER="https://staging-container.sandbox.googleapis.com/" | ||
| export E2E_NAME="jkns-gke-e2e-staging-trusty" | ||
| export KUBE_OS_DISTRIBUTION="trusty" | ||
| - 'gke-trusty-staging-parallel': | ||
| description: 'Run E2E tests on GKE staging endpoint in parallel.' | ||
| timeout: 80 | ||
| job-env: | | ||
| export PROJECT="e2e-gke-trusty-staging-p" | ||
| export CLOUDSDK_BUCKET="gs://cloud-sdk-testing/rc" | ||
| export JENKINS_USE_SERVER_VERSION="y" | ||
| export CLOUDSDK_API_ENDPOINT_OVERRIDES_CONTAINER="https://staging-container.sandbox.googleapis.com/" | ||
| export GINKGO_TEST_ARGS="--ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]" | ||
| export GINKGO_PARALLEL="y" | ||
| export E2E_NAME="jkns-gke-e2e-staging-parallel-trusty" | ||
| export KUBE_OS_DISTRIBUTION="trusty" | ||
| - 'gke-trusty-prod': | ||
| # Failing constantly due to a known issue (tracked internally). | ||
| disable_job: true | ||
| description: 'Run E2E tests on GKE prod endpoint.' | ||
| timeout: 480 | ||
| job-env: | | ||
| export PROJECT="kubekins-e2e-gke-trusty-prod" | ||
| export CLOUDSDK_BUCKET="gs://cloud-sdk-testing/rc" | ||
| export JENKINS_USE_SERVER_VERSION="y" | ||
| export KUBE_GCE_ZONE="asia-east1-b" | ||
| export E2E_NAME="jkns-gke-e2e-prod-trusty" | ||
| export KUBE_OS_DISTRIBUTION="trusty" | ||
| - 'gke-trusty-prod-parallel': | ||
| # Failing constantly due to a known issue (tracked internally). | ||
| disable_job: true | ||
| description: 'Run E2E tests on GKE prod endpoint in parallel.' | ||
| timeout: 80 | ||
| job-env: | | ||
| export PROJECT="e2e-gke-trusty-prod-p" | ||
| export CLOUDSDK_BUCKET="gs://cloud-sdk-testing/rc" | ||
| export JENKINS_USE_SERVER_VERSION="y" | ||
| export GINKGO_TEST_ARGS="--ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]" | ||
| export GINKGO_PARALLEL="y" | ||
| export KUBE_GCE_ZONE="asia-east1-b" | ||
| export E2E_NAME="jkns-gke-e2e-prod-parallel-trusty" | ||
| export KUBE_OS_DISTRIBUTION="trusty" | ||
| jobs: | ||
| - 'kubernetes-e2e-{suffix}' | ||
| #============================== End of Trusty jobs ============================= | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you want to use the RC
gcloud?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i.e. you probably shouldn't be. 😉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I copied
job-envs from the equivalentgke-testjob. We have been using the same configs and I think we want to keep doing so. For Trusty, we want to make sure it passes whatever tests that GKE has with ContainerVM. cc/ @roberthbaileySame for other jobs.