-
Notifications
You must be signed in to change notification settings - Fork 84
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
ci: use bazel cache #19
Comments
Currently blocking on the creation of the envoy-mobile repo and for it to begin using CircleCI. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions. |
What's the blocker here now? Also note I'm working with Google to try remote execution with this project |
No blocker @keith. We were waiting to get the project moved to this repo, open sourced, and ready with CI. Now that that is all done this issue is open to be worked on. If you want to take it on that would be awesome! I am taking the liberty to assign you :) |
CI uses bazel cache and remote exec thanks to EngFlow. |
Enable use of a bazel cache
The text was updated successfully, but these errors were encountered: