build: fix bazel not available if cache could not be restored #16764
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.
Currently the
setup_bazel_binary
script always runs beforethe node modules are installed. This means that the the
global bazel binary cannot be set up as the
@bazel/bazel
package is not installed yet.
Due to CircleCI's caching (and fallback caching) we currently
have a lot of cache hits that prevented this issue from showing
up (until https://circleci.com/gh/angular/components/70351)