Skip to content
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

fix(bazel): pass custom bazel compiler host rather than rewriting one #31496

Closed
wants to merge 1 commit into from

Conversation

ayazhafiz
Copy link
Member

Switch back to passing a custom bazel host instead of rewriting one that
is passed to compile now that the Angular indexer is stable.

Revert "feat(bazel): allow passing and rewriting an old bazel host"

This reverts commit 0a4c1c8.

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Rewrites an old bazel host.

Issue Number: N/A

What is the new behavior?

User has to define their own bazel host

Does this PR introduce a breaking change?

  • Yes
  • No

Should only impact the Angular indexer inside Google. This change is has not been documented and announced publicly.

Switch back to passing a custom bazel host instead of rewriting one that
is passed to `compile` now that the Angular indexer is stable.

Revert "feat(bazel): allow passing and rewriting an old bazel host"

This reverts commit 0a4c1c8.
@ayazhafiz ayazhafiz requested a review from a team as a code owner July 10, 2019 20:31
@ayazhafiz ayazhafiz requested a review from kyliau July 10, 2019 20:32
@ayazhafiz ayazhafiz self-assigned this Jul 10, 2019
@ayazhafiz ayazhafiz added area: bazel Issues related to the published `@angular/bazel` build rules target: major This PR is targeted for the next major release refactoring Issue that involves refactoring or code-cleanup labels Jul 10, 2019
@ngbot ngbot bot modified the milestone: needsTriage Jul 10, 2019
@ayazhafiz ayazhafiz added the action: merge The PR is ready for merge by the caretaker label Jul 11, 2019
@matsko matsko closed this in 0c61a35 Jul 12, 2019
@ayazhafiz ayazhafiz deleted the feature/old-bazel-host branch July 12, 2019 15:50
sabeersulaiman pushed a commit to sabeersulaiman/angular that referenced this pull request Sep 6, 2019
…angular#31496)

Switch back to passing a custom bazel host instead of rewriting one that
is passed to `compile` now that the Angular indexer is stable.

Revert "feat(bazel): allow passing and rewriting an old bazel host"

This reverts commit 0a4c1c8.

PR Close angular#31496
@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 15, 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 area: bazel Issues related to the published `@angular/bazel` build rules cla: yes refactoring Issue that involves refactoring or code-cleanup target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants