-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[Tracker] Migrate prow tests to GitHub Action #10744
Comments
/remove-kind bug |
@rimolive: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
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. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
/lifecycle frozen |
Description
Kubeflow Pipelines CI uses Google's Prow infrastructure to run the tests for frontent and backend, as well as trigger pre and post submit tests for PRs. With the growing number of contributors in Kubeflow Pipelines, and the limitations to troubleshoot integration tests or run locally, we propose migrate to GitHub Actions to make tests easier to run, trackable through artifact generation, and optionally able to run locally.
On another note, as part of CNCF graduation, we plan to use the GitHub hosted runners to make tests run faster, thus speeding up the process of PR reviews/approvals
Below is a list of the tests that needs to be migrated (we will create an issue for each test):
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered: