Limit Bazel memory usage in CI. #1183
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This aims to reduce/eliminate the CircleCI flakes described in grpc-ecosystem#968. It's based on the approach in https://github.com/angular/angular-cli/blob/master/.circleci/bazel.rc
johanbrandhorst
approved these changes
Mar 23, 2020
|
FWIW I'm not sure that this will help - bazelbuild/rules_typescript#380 suggests that the workaround wasn't sufficient in their case, and that they had to use a large instance, which requires the Performance Plan. Could be worth keeping the issue open and revisiting the next time the stale[bot] jumps in. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This aims to reduce/eliminate the CircleCI flakes described in #968.
It's based on the approach in
https://github.com/angular/angular-cli/blob/master/.circleci/bazel.rc