You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
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.
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: