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

Migration of etcd-io/etcd GitHub Actions to Prow #32754

Open
1 of 15 tasks
ArkaSaha30 opened this issue Jun 14, 2024 · 6 comments
Open
1 of 15 tasks

Migration of etcd-io/etcd GitHub Actions to Prow #32754

ArkaSaha30 opened this issue Jun 14, 2024 · 6 comments
Assignees
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/etcd Categorizes an issue or PR as relevant to SIG Etcd.

Comments

@ArkaSaha30
Copy link
Member

ArkaSaha30 commented Jun 14, 2024

What should be cleaned up or changed:
As a part of the migration, following GitHub Actions running as presubmits/postsubmits/periodics may need to be migrated to Prow:

main :

release-3.5 :

release-3.4 :

Provide any links for context:
Parent Issue ref: kubernetes/k8s.io#6102

@ArkaSaha30 ArkaSaha30 added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Jun 14, 2024
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jun 14, 2024
@ArkaSaha30
Copy link
Member Author

This is an initial list of GitHub workflows I have identified for the migration, please review the list if anything needs to be added/removed.

/sig etcd

@k8s-ci-robot k8s-ci-robot added sig/etcd Categorizes an issue or PR as relevant to SIG Etcd. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jun 14, 2024
@ArkaSaha30
Copy link
Member Author

/assign

cc @jmhbnz @ahrtr @serathius

@ahrtr
Copy link
Member

ahrtr commented Jun 14, 2024

Also link to kubernetes/k8s.io#6102

@ivanvc
Copy link
Member

ivanvc commented Jun 21, 2024

I wasn't aware of this task. Watching now.

@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue 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 3, 2024
@ivanvc
Copy link
Member

ivanvc commented Dec 3, 2024

/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 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/etcd Categorizes an issue or PR as relevant to SIG Etcd.
Projects
None yet
Development

No branches or pull requests

5 participants