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

Add transfer Issue plugin to Kubeflow repos #2331

Conversation

andreyvelich
Copy link
Contributor

I added cherrypicker and transfer issue plugins to the Kubeflow repos:

This should help us with Kubeflow repo migration: kubeflow/kubeflow#7549

Also, added kubeflow/dashboard repo to the Kubeflow list.

/hold for review

/cc @rimolive @terrytangyuan @kimwnasptd @thesuperzapper @StefanoFioravanzo @zijianjoy @johnugeorge @jbottum @james-jwu

Copy link
Contributor

@andreyvelich: GitHub didn't allow me to request PR reviews from the following users: terrytangyuan, johnugeorge, StefanoFioravanzo, jbottum, rimolive, kimwnasptd, thesuperzapper.

Note that only GoogleCloudPlatform members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

I added cherrypicker and transfer issue plugins to the Kubeflow repos:

This should help us with Kubeflow repo migration: kubeflow/kubeflow#7549

Also, added kubeflow/dashboard repo to the Kubeflow list.

/hold for review

/cc @rimolive @terrytangyuan @kimwnasptd @thesuperzapper @StefanoFioravanzo @zijianjoy @johnugeorge @jbottum @james-jwu

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-sigs/prow repository.

Copy link
Contributor

Hi @andreyvelich. Thanks for your PR.

I'm waiting for a GoogleCloudPlatform member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

Copy link
Contributor

@terrytangyuan terrytangyuan left a comment

Choose a reason for hiding this comment

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

/lgtm

Copy link
Contributor

@terrytangyuan: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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-sigs/prow repository.

@thesuperzapper
Copy link
Contributor

@andreyvelich we need to ask a googler for review.

We should also set up a policy around which situations warrant a repo transfer for an issue, especially for cases where there is ambiguity.

In cases where things are very ambiguous (technical discussions covering multiple components), I think we should use kubeflow/kubeflow, rather than community or manifests.

And keep those repos for things directly related to their contents.

@andreyvelich
Copy link
Contributor Author

Copy link
Contributor

@andreyvelich: GitHub didn't allow me to assign the following users: fejta, mpherman2.

Note that only GoogleCloudPlatform members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

Sure.
/assign @chaodaiG @chases2 @cjwagner @fejta @michelle192837 @mpherman2

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-sigs/prow repository.

@andreyvelich
Copy link
Contributor Author

In cases where things are very ambiguous (technical discussions covering multiple components)

Why we can't use kubeflow/manifests for Kubeflow platform questions (cc @juliusvonkohout) or kubeflow/community for the new project adoption and questions for the community direction?
We can always reconsider it in the future, if that won't work for us.

I feel that it will be really hard to triage issues under kubeflow/kubeflow for community members and our users will feel bad about it.

@andreyvelich
Copy link
Contributor Author

Additionally, I added trigger plugin to the Kubeflow: https://prow.k8s.io/command-help#ok_to_test.
That will allow us to add /ok-to-test label to the PRs and trigger GitHub actions with /rerun-all command. Currently, you have to have write access to add this label to the PR.

We already use this GitHub action in several repos (Pipelines, Katib, Training Operator) to re-trigger GitHub actions using PR comments: https://github.com/estroz/rerun-actions.
This actions expect ok-to-test label to be present.

cc @rimolive

@cjwagner
Copy link
Member

/test all
/approve

@andreyvelich
Copy link
Contributor Author

/retest

Copy link
Contributor

@andreyvelich: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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-sigs/prow repository.

@cjwagner
Copy link
Member

/ok-to-test

@google-oss-prow google-oss-prow bot added size/M and removed size/S labels Jul 30, 2024
@rimolive
Copy link

I'm good with the changes.

@andreyvelich
Copy link
Contributor Author

@thesuperzapper Do you know if I setup the cherrypicker plugin correctly ?
I just follow the same config as for Kubernetes prow: https://github.com/kubernetes/test-infra/blob/ab0aea453361484ad834f42c7cb633f5f74a3535/config/prow/plugins.yaml#L1826.

@andreyvelich
Copy link
Contributor Author

@rimolive @terrytangyuan @kimwnasptd @thesuperzapper @StefanoFioravanzo @zijianjoy @johnugeorge @jbottum @james-jwu Anything you want to add before merging this PR ?

@rimolive
Copy link

rimolive commented Aug 7, 2024

No other things to add. Thanks @andreyvelich for working in this PR.

@andreyvelich
Copy link
Contributor Author

@zijianjoy @chensun @james-jwu @chaodaiG @chases2 @cjwagner @fejta @michelle192837 @mpherman2 Please can you help us to LGTM this PR ?

@andreyvelich
Copy link
Contributor Author

/hold cancel

Copy link
Member

@cjwagner cjwagner left a comment

Choose a reason for hiding this comment

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

I'm not sure how much work it would take to set up the cherrypicker external-plugin for this Prow instance. If that is something you would like can you please open a separate GitHub issue requesting that?

If you remove the external_plugins section for now I can approve the rest of this PR though.

events:
- issue_comment
- pull_request
endpoint: http://cherrypicker
Copy link
Member

Choose a reason for hiding this comment

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

There is no cherrypicker service deployed on this Prow instance so there won't be anything to reach at this endpoint.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I see, thanks for checking @cjwagner! I will create separate issue and remove it from this PR.

Choose a reason for hiding this comment

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

I tested it with kubeflow/manifests#2837 (comment) and it worked out fine.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Amazing, thank you @juliusvonkohout!

@google-oss-prow google-oss-prow bot removed the approved label Aug 8, 2024
@google-oss-prow google-oss-prow bot added size/S and removed size/M labels Aug 8, 2024
@andreyvelich andreyvelich changed the title Add cherrypicker and transfer Issue plugins to Kubeflow repos Add transfer Issue plugins to Kubeflow repos Aug 8, 2024
@andreyvelich andreyvelich changed the title Add transfer Issue plugins to Kubeflow repos Add transfer Issue plugin to Kubeflow repos Aug 8, 2024
@google-oss-prow google-oss-prow bot added the lgtm label Aug 8, 2024
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreyvelich, cjwagner, terrytangyuan

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

@google-oss-prow google-oss-prow bot merged commit 0015432 into GoogleCloudPlatform:master Aug 8, 2024
5 checks passed
Copy link
Contributor

@andreyvelich: Updated the plugins configmap in namespace default at cluster default using the following files:

  • key plugins.yaml using file prow/oss/plugins.yaml

In response to this:

I added cherrypicker and transfer issue plugins to the Kubeflow repos:

This should help us with Kubeflow repo migration: kubeflow/kubeflow#7549

Also, added kubeflow/dashboard repo to the Kubeflow list.

/hold for review

/cc @rimolive @terrytangyuan @kimwnasptd @thesuperzapper @StefanoFioravanzo @zijianjoy @johnugeorge @jbottum @james-jwu

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.

@andreyvelich andreyvelich deleted the update-kubeflow-plugins branch August 9, 2024 10:03
@@ -338,33 +341,11 @@ plugins:
- project # Lets issues be tagged into projects
- size
- skip # Allows cleaning up stale commit statuses
- transfer-issue # Transfer issue to a different repo in the same org.
- trigger # Enable /ok-to-test command to trigger GitHub actions with /rerun-all
Copy link
Contributor

@hbelmiro hbelmiro Aug 13, 2024

Choose a reason for hiding this comment

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

@andreyvelich if my understanding is correct, /ok-to-test should trigger GitHub Actions after this change. But it didn't.
Screenshot from 2024-08-13 12-57-51

Do you know if there's anything else that we should do, or is that a bug?

cc @rimolive @DharmitD

Copy link
Contributor Author

@andreyvelich andreyvelich Aug 13, 2024

Choose a reason for hiding this comment

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

@hbelmiro This plugin just adds ok-to-test label to the PR after we add this comment: /ok-to-test.
It doesn't trigger the GitHub actions.
Since we use this action to trigger our action: https://github.com/estroz/rerun-actions, you need to add this comment to trigger the actions:

/rerun-all

Copy link
Contributor

Choose a reason for hiding this comment

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

I see.
The comment made me think that /ok-to-test would somehow automatically trigger /rerun-all.
Thank you @andreyvelich.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants