Skip to content

build: fix bazel not available if cache could not be restored #16764

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

Conversation

devversion
Copy link
Member

Currently the setup_bazel_binary script always runs before
the 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)

Currently the `setup_bazel_binary` script always runs before
the 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)
@devversion devversion requested a review from jelbourn as a code owner August 13, 2019 15:43
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 13, 2019
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Aug 13, 2019
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Aug 13, 2019
@ngbot
Copy link

ngbot bot commented Aug 13, 2019

I see that you just added the pr: merge ready label, but the following checks are still failing:
    failure status "ci/circleci: tests_browserstack" is failing

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

@jelbourn jelbourn merged commit 417adf8 into angular:master Aug 13, 2019
mmalerba pushed a commit that referenced this pull request Aug 14, 2019
Currently the `setup_bazel_binary` script always runs before
the 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)

(cherry picked from commit 417adf8)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants