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

jobs: remove jobs that use --gke-environment=test #17213

Merged
merged 12 commits into from
Apr 15, 2020

Conversation

spiffxp
Copy link
Member

@spiffxp spiffxp commented Apr 15, 2020

these shouldn't be running on prow.k8s.io

this uses --gke-environment=test, which should be dropped
from prow.k8s.io

hasn't been run since 2019-06-10
this uses --gke-environment=test, which should be dropped
from prow.k8s.io

hasn't been run since 2018-05-25
all of these use --gke-environment=test, which should be dropped
from prow.k8s.io

none of these have passed since 2019-05-30
all of these use --gke-environment=test, which should be dropped
from prow.k8s.io

none of these have passed since 2019-12-18
all of these use --gke-environment=test, which should be dropped
from prow.k8s.io

none of these have passed since 2019-12-18

removed associated testgrid entries as well
all of these use --gke-environment=test, which should be dropped
from prow.k8s.io

none of these have passed since 2019-10-29
this uses --gke-environment=test, which should be dropped
from prow.k8s.io

this has not ever passed
these use --gke-environment=test, which should be dropped
from prow.k8s.io

these have not passed since 2020-02-11
thise uses --gke-environment=test, which should be dropped
from prow.k8s.io

this has not ever passed
these use --gke-environment=test, which should be dropped
from prow.k8s.io

these have not passed since 2019-10-29

remove associated testgrid entries
these use --gke-environment=test, which should be dropped
from prow.k8s.io

these have not passed since 2019-11-04

remove associated testgrid entries
these use --gke-environment=test, which should be dropped
from prow.k8s.io

these have not passed since 2019-10-29

remove associated testgrid entries and update README
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. area/config Issues or PRs related to code in /config area/provider/gcp Issues or PRs related to gcp provider area/release-eng Issues or PRs related to the Release Engineering subproject area/testgrid sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels Apr 15, 2020
@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 15, 2020
@spiffxp spiffxp requested review from liggitt and removed request for bskiba April 15, 2020 03:37
@spiffxp spiffxp removed the request for review from andrewsykim April 15, 2020 03:37
@spiffxp
Copy link
Member Author

spiffxp commented Apr 15, 2020

/hold
for requested reviewers

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 15, 2020
@liggitt
Copy link
Member

liggitt commented Apr 15, 2020

lgtm but will defer to @sebastienvas

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 15, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sebastienvas, spiffxp

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@spiffxp
Copy link
Member Author

spiffxp commented Apr 15, 2020

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 15, 2020
@k8s-ci-robot k8s-ci-robot merged commit ee2bcec into kubernetes:master Apr 15, 2020
@k8s-ci-robot
Copy link
Contributor

@spiffxp: Updated the job-config configmap in namespace default at cluster default using the following files:

  • key gke-test-containerd.yaml using file ``
  • key generated.yaml using file config/jobs/kubernetes/generated/generated.yaml
  • key sig-autoscaling-config.yaml using file config/jobs/kubernetes/sig-autoscaling/sig-autoscaling-config.yaml
  • key sig-cli-config.yaml using file config/jobs/kubernetes/sig-cli/sig-cli-config.yaml
  • key gcp-gke.yaml using file ``
  • key gcp-gpu-presubmits.yaml using file config/jobs/kubernetes/sig-cloud-provider/gcp/gpu/gcp-gpu-presubmits.yaml
  • key gpu-gke.yaml using file ``
  • key upgrade-gke.yaml using file ``
  • key sig-instrumentation-config.yaml using file config/jobs/kubernetes/sig-instrumentation/sig-instrumentation-config.yaml
  • key sig-network-misc.yaml using file config/jobs/kubernetes/sig-network/sig-network-misc.yaml
  • key 1.15.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.15.yaml
  • key 1.16.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.16.yaml
  • key 1.17.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.17.yaml
  • key 1.18.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.18.yaml

In response to this:

these shouldn't be running on prow.k8s.io

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/config Issues or PRs related to code in /config area/provider/gcp Issues or PRs related to gcp provider area/release-eng Issues or PRs related to the Release Engineering subproject area/testgrid cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants