-
Notifications
You must be signed in to change notification settings - Fork 195
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
Remove Bazel from cloud-provider-gcp and use make to build it #587
Comments
This issue is currently awaiting triage. If the repository mantainers determine this is a relevant issue, they will accept it by applying the The 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. |
/sig testing |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
There has been 3 attempts so far which haven't really gone anywhere.
Unfortunately, I want to start using kubetest2 more widely to test e2e scenarios for 1.29 and replace kubetest for kubernetes/enhancements#2464 but using bazel in a critical path might block wider adoption. We removed bazel in 1.23 kubernetes/enhancements#2420kubetest2 can run in legacy mode where it uses the build and cluster scripts in the k/k repo.
I'm happy to make another attempt and complete 259 if I can find sufficient approvers for this work.
The text was updated successfully, but these errors were encountered: