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

KEP: (sig-testing) Continuously Deploy K8s Prow #2539

Closed
4 tasks
chaodaiG opened this issue Feb 23, 2021 · 23 comments
Closed
4 tasks

KEP: (sig-testing) Continuously Deploy K8s Prow #2539

chaodaiG opened this issue Feb 23, 2021 · 23 comments
Assignees
Labels
kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Milestone

Comments

@chaodaiG
Copy link
Contributor

chaodaiG commented Feb 23, 2021

Enhancement Description

  • One-line enhancement description (can be used as a release note): Continuously Deploy K8s Prow
  • Kubernetes Enhancement Proposal: KEP: (sig-testing) continuously deploy k8s prow #2540
  • Discussion Link: SIG Testing 2020-02-23 (video) (meeting notes)
  • Primary contact (assignee): chaodaiG
  • Responsible SIGs: sig-testing
  • Alpha
    • KEP (k/enhancements) update PR(s):
    • Code (k/k) update PR(s):
    • Docs (k/website) update PR(s):
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Feb 23, 2021
@chaodaiG
Copy link
Contributor Author

chaodaiG commented Feb 23, 2021

/sig sig-testing sig-release

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Feb 23, 2021

@chaodaiG: The label(s) sig/sig-testing, sig/sig-release cannot be applied, because the repository doesn't have them

In response to this:

/sig sig-testing sig-release

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.

@chaodaiG
Copy link
Contributor Author

chaodaiG commented Feb 23, 2021

/sig sig-testing

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Feb 23, 2021

@chaodaiG: The label(s) sig/sig-testing cannot be applied, because the repository doesn't have them

In response to this:

/sig sig-testing

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.

@chaodaiG
Copy link
Contributor Author

chaodaiG commented Feb 23, 2021

/sig testing

@k8s-ci-robot k8s-ci-robot added sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 23, 2021
@spiffxp
Copy link
Member

spiffxp commented Mar 5, 2021

/priority important-soon

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Mar 5, 2021
@spiffxp spiffxp added this to To Triage in sig-testing issues via automation Mar 5, 2021
@spiffxp spiffxp added the tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team label Mar 5, 2021
@spiffxp
Copy link
Member

spiffxp commented Mar 5, 2021

I would bucket this KEP under process when #2311 is completed

@spiffxp
Copy link
Member

spiffxp commented Mar 10, 2021

/sig release
/milestone v1.21
(this depends on timeline, re: #2553 (comment))

@k8s-ci-robot k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Mar 10, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Mar 10, 2021
@spiffxp
Copy link
Member

spiffxp commented Mar 10, 2021

@chaodaiG I updated the discussion links for you

@fejta-bot
Copy link

fejta-bot commented Jun 8, 2021

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 8, 2021
@chaodaiG
Copy link
Contributor Author

chaodaiG commented Jun 8, 2021

This was done
/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Jun 8, 2021

@chaodaiG: Closing this issue.

In response to this:

This was done
/close

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.

sig-testing issues automation moved this from To Triage to Done Jun 8, 2021
@spiffxp
Copy link
Member

spiffxp commented Jun 9, 2021

/remove-lifecycle stale
/reopen
@chaodaiG I'm not sure this is done?

So my read is we're at beta

@k8s-ci-robot k8s-ci-robot reopened this Jun 9, 2021
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Jun 9, 2021

@spiffxp: Reopened this issue.

In response to this:

/remove-lifecycle stale
/reopen
@chaodaiG I'm not sure this is done?

So my read is we're at beta

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.

sig-testing issues automation moved this from Done to Backlog Jun 9, 2021
@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 9, 2021
@chaodaiG
Copy link
Contributor Author

chaodaiG commented Jun 9, 2021

So my read is we're at beta

That's correct. I misread the policy

@spiffxp spiffxp added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team labels Aug 17, 2021
@spiffxp
Copy link
Member

spiffxp commented Aug 17, 2021

/stage beta

@k8s-ci-robot k8s-ci-robot added the stage/beta Denotes an issue tracking an enhancement targeted for Beta status label Aug 17, 2021
@spiffxp
Copy link
Member

spiffxp commented Sep 10, 2021

/kind kep

@k8s-triage-robot
Copy link

k8s-triage-robot commented Dec 9, 2021

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 9, 2021
@spiffxp
Copy link
Member

spiffxp commented Dec 10, 2021

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 10, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Mar 11, 2022

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 11, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Apr 10, 2022

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 10, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented May 10, 2022

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented May 10, 2022

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.

sig-testing issues automation moved this from Backlog to Done May 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
Development

No branches or pull requests

5 participants