Skip to content

build: bazel not working on windows workaround #15484

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

Recently we updated our Bazel setup to Angular V8 beta. With that change
the Sass dependencies took precedence and now fetch the skylib repository
using the git_repository bazel rule. Unfortunately this rule does not always
work as expected in Windows (e.g. when used within Git Bash). Until Bazel
drops the dependency on bash, we should make sure that we fetch skylib
through the http_archive rule (which works on windows). Skylib will be
transitively brought in by the rules_webtesting repository.

Recently we updated our Bazel setup to Angular V8 beta. With that change
the Sass dependencies took precedence and now fetch the skylib repository
using the `git_repository` bazel rule. Unfortunately this rule does not always
work as expected in Windows (e.g. when used within Git Bash). Until Bazel
drops the dependency on bash, we should make sure that we fetch skylib
through the `http_archive` rule (which works on windows). Skylib will be
transitively brought in by the `rules_webtesting` repository.
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Mar 14, 2019
@devversion devversion requested a review from jelbourn as a code owner March 14, 2019 18:37
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 14, 2019
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 Mar 21, 2019
@ngbot
Copy link

ngbot bot commented Mar 21, 2019

I see that you just added the pr: merge ready label, but the following checks are still failing:
    failure status "branch-manager" 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.

@andrewseguin andrewseguin merged commit a1762cc into angular:master Mar 22, 2019
@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 10, 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.

5 participants