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

Enable Prow plugins for etcd PRs #18110

Open
ArkaSaha30 opened this issue Jun 3, 2024 · 9 comments
Open

Enable Prow plugins for etcd PRs #18110

ArkaSaha30 opened this issue Jun 3, 2024 · 9 comments
Assignees
Labels
area/tooling priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. type/feature

Comments

@ArkaSaha30
Copy link
Contributor

ArkaSaha30 commented Jun 3, 2024

What would you like to be added?

Plugin enablement for etcd in test-infra.
Suggested plugins to be added:

Why is this needed?

There are useful Prow plugins that etcd can leverage to minimize manual efforts. One of them is the cherrypicker plugin, which can backport any PR to a specific branch with just a /cherry-pick <branch_name> comment on the PR.
Example: containerd/containerd#10257 (comment)

@ArkaSaha30
Copy link
Contributor Author

cc @ahrtr @jmhbnz

@ahrtr
Copy link
Member

ahrtr commented Jun 3, 2024

Sounds good to me. /cherry-pick might work for 3.5, but not for 3.4, which has huge difference with main.

@jmhbnz jmhbnz added area/tooling priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Jun 3, 2024
@jmhbnz
Copy link
Member

jmhbnz commented Jun 3, 2024

Thanks for proposing this @ArkaSaha30. Enabling the cherry pick plugin makes sense to me, please feel free to raise a pr if you have capacity 🙏🏻

@ArkaSaha30
Copy link
Contributor Author

/assign

ArkaSaha30 pushed a commit to ArkaSaha30/test-infra that referenced this issue Jun 4, 2024
This commit will add cherrypicker external plugin
for etcd-io/etcd repo.
Issue ref: etcd-io/etcd#18110

Signed-off-by: arkas1 <[email protected]>
ArkaSaha30 pushed a commit to ArkaSaha30/test-infra that referenced this issue Jun 4, 2024
This commit will add cherrypicker external plugin
for etcd-io/etcd repo.
Issue ref: etcd-io/etcd#18110

Signed-off-by: arkas1 <[email protected]>
ArkaSaha30 added a commit to ArkaSaha30/test-infra that referenced this issue Jun 4, 2024
This commit will add cherrypicker external plugin
for etcd-io/etcd repo.
Issue ref: etcd-io/etcd#18110

Signed-off-by: ArkaSaha30 <[email protected]>
@jmhbnz
Copy link
Member

jmhbnz commented Jun 6, 2024

Hi @ArkaSaha30 - We raised this at sig-etcd triage meeting, are there any other plugins you suggest we enable or can we close this now?

@ivanvc
Copy link
Member

ivanvc commented Jun 6, 2024

Based on kubernetes/k8s.io#6102 (comment), do we also want to enable tide, lgtm, and approve?

@ArkaSaha30
Copy link
Contributor Author

Based on kubernetes/k8s.io#6102 (comment), do we also want to enable tide, lgtm, and approve?

Yes! Along with these we can also add 'size' which will label the PRs based on how lengthy it is. WDYT @jmhbnz ?

@jmhbnz
Copy link
Member

jmhbnz commented Jun 7, 2024

Based on kubernetes/k8s.io#6102 (comment), do we also want to enable tide, lgtm, and approve?

I am not confident we are ready as a project for tide / auto merging of pull requests. It would be helpful to update this issue with a description of what the proposed plugin does and what impact this would have for the etcd project.

I am happy to enable the pr sizing plugin as that is very low risk.

@jmhbnz
Copy link
Member

jmhbnz commented Dec 5, 2024

Discussed during sig-etcd triage meeting, the next major step for this issue is to enable tide for automatically merging pull requests.

This will be a significant change for etcd-io/etcd so we need to discuss this more broadly and ensure the community is ready, next steps would be:

  • Discuss at a community meeting - Added agenda item
  • Raise a #sig-etcd slack discussion
  • Add a detailed comment here with the behavior for tide
  • Draft a pull request with a /hold

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tooling priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. type/feature
Development

No branches or pull requests

4 participants