Skip to content

build: prevent bazel from logging warning on each invocation #19298

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

Merged
merged 1 commit into from
May 13, 2020

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented May 9, 2020

Each time ibazel is run, it logs something like:

INFO: Build completed successfully, 14 total actions

################################################################################
# Did you know iBazel can invoke programs like Gazelle, buildozer, and         #
# other BUILD file generators for you automatically based on bazel output?     #
# Documentation at: https://github.com/bazelbuild/bazel-watcher#output-runner  #
################################################################################

iBazel [3:24PM]: Use default regex

These changes avoid the annoying banner by adding a .bazel_fix_commands.json file according to https://github.com/bazelbuild/bazel-watcher#output-runner. Note that we it seems like we should be able to do the same by passing the --run_output=false flag, but I wasn't able to get it to work through the .bazelrc.

Each time ibazel is run, it logs something like:

```
INFO: Build completed successfully, 14 total actions

################################################################################
# Did you know iBazel can invoke programs like Gazelle, buildozer, and         #
# other BUILD file generators for you automatically based on bazel output?     #
# Documentation at: https://github.com/bazelbuild/bazel-watcher#output-runner  #
################################################################################

iBazel [3:24PM]: Use default regex
```

These changes avoid the annoying banner by adding a `.bazel_fix_commands.json` file according to https://github.com/bazelbuild/bazel-watcher#output-runner. Note that we it seems like we should be able to do the same by passing the `--run_output=false` flag, but I wasn't able to get it to work through the `.bazelrc`.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent merge safe target: patch This PR is targeted for the next patch release labels May 9, 2020
@crisbeto crisbeto requested review from jelbourn and a team as code owners May 9, 2020 13:31
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 9, 2020
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

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

LGTM. Should we submit an issue upstream? I assume a comment in the file would be nice, but it's not JSON5 so we cannot right?

@devversion devversion added lgtm action: merge The PR is ready for merge by the caretaker labels May 11, 2020
@crisbeto
Copy link
Member Author

I don't know whether we should file an issue, because it's documented which makes me think that it works this way on purpose.

@devversion
Copy link
Member

I don't think we should file an issue for the feature they are advertising for, but rather we should file an issue for the "ad banner" that is undesired in some Bazel projects. A way to reasonably disable the advertisement is not documented either.

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

@mmalerba mmalerba merged commit 9377b49 into angular:master May 13, 2020
@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 Jun 13, 2020
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 P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent 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