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.

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

Track most remaining Jenkins E2E jobs. #19301

Merged
merged 1 commit into from
Jan 12, 2016
Merged

Conversation

spxtr
Copy link
Contributor

@spxtr spxtr commented Jan 5, 2016

This leaves these e2e jobs untracked:

  • kubernetes-e2e-gce-enormous-cluster
  • kubernetes-e2e-gce-examples
  • kubernetes-e2e-gce-trusty-*

I noticed that the gke jobs email cloud-kubernetes-alerts@ as well as cloud-kubernetes-team@ . Is that necessary, or should I get rid of that?

gke-flaky exports these in its job config, which aren't necessary:

export E2E_DOWN=true
export KUBERNETES_PROVIDER=gke
export E2E_ZONE=us-central1-f

gce-release-1.0 exports this in its job config, unnecessary:

export JENKINS_PUBLISHED_VERSION="ci/latest-1.0"

gce-disruptive-1.1 exports this in its job config, which should likely be included in release-1.1's e2e.sh case:

export TEST_CLUSTER_LOG_LEVEL="--v=4"

#18122. Please do not add LGTM tag. I'll merge manually to watch Jenkins. I did not backup these job configs.

@k8s-github-robot
Copy link

Labelling this PR as size/M

@k8s-github-robot k8s-github-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jan 5, 2016
@k8s-bot
Copy link

k8s-bot commented Jan 5, 2016

GCE e2e test build/test passed for commit 3619fb5a41314a410cad8feb29b139f3f1fc73b6.

- project:
name: kubernetes-e2e-1.1
trigger-job: 'kubernetes-build-1.1'
test-owner: 'GKE on-call'
Copy link
Member

Choose a reason for hiding this comment

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

I wonder if maybe we should keep the GKE builds separate here? Having the GKE-specific text and then immediately overriding it for the gce- builds seems weird.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agreed, fixed. I also had some of the descriptions wrong, that's fixed now too.

@k8s-bot
Copy link

k8s-bot commented Jan 6, 2016

GCE e2e test build/test passed for commit 61ee06f14e03da35f6bf648caf20e3f6aaa391cc.

@k8s-github-robot
Copy link

Labelling this PR as size/L

@k8s-github-robot k8s-github-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 7, 2016
@spxtr
Copy link
Contributor Author

spxtr commented Jan 7, 2016

@ixdy made some changes, PTAL. Notably I made the emails send out to the proper places.

@ihmccreery this is how to set emails recipients if you are using this format for your upgrade jobs. For yours you might as well just set the email to yourself in the template, instead of using a variable + global default, since you'll override it for every job anyway.

@k8s-bot
Copy link

k8s-bot commented Jan 7, 2016

GCE e2e test build/test passed for commit edc274b.

@ixdy
Copy link
Member

ixdy commented Jan 9, 2016

LGTM

@spxtr
Copy link
Contributor Author

spxtr commented Jan 12, 2016

Manual merge to watch Jenkins.

spxtr added a commit that referenced this pull request Jan 12, 2016
Track most remaining Jenkins E2E jobs.
@spxtr spxtr merged commit 2a72ff5 into kubernetes:master Jan 12, 2016
@spxtr spxtr deleted the job-configs branch January 12, 2016 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test-infra size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants