-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Run tests via prow #276
Comments
/help-wanted |
/priority important-longterm |
/help-wanted |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
@DirectXMan12 Is this still desired or are you considering GitHub actions instead? |
yeah, I'd still like to do this. I'd love for GitHub actions to work out, but I expect there'll be issues around GitHub actions' interaction with forks during the beta period. AIUI (can't test, actions seems to be borked for k-sigs ATM), this'll make actions unusable till they're on by default. |
we need something better than travis in the mean time |
/assign |
Add categories to the CRD installed by the controller
We should be running our test suite in prow instead of Travis, so the normal kube workflow commands work.
The text was updated successfully, but these errors were encountered: