commit | 62dd17438bcde06ccbed361f6594a6cf96fb3a07 | [log] [tgz] |
---|---|---|
author | philwo <philwo@google.com> | Tue Jun 04 05:27:37 2019 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Jun 04 05:28:24 2019 -0700 |
tree | dd893126a6b1b338f614a4a0e9261aa65182caed | |
parent | b7eca20d79fa1b1f8c4006c6dd41fc6dc1cdc055 [diff] |
Add the flag --auto_output_filter=[none,all,packages,subpackages] to Bazel. While compiler warnings and debugging output can be valuable, they can also make your build log hard to read: Ever had the problem of spotting an error in 150.000 lines of compiler warnings? Or do you only want to see warnings that come from the code you're actually working on? Bazel now has a flag to help you out: With the new flag --auto_output_filter=[none,all,packages,subpackages] you can instruct Bazel to not print any warnings (--auto_output_filter=all), print only warnings from the packages explicitly listed as targets on your command-line (--auto_output_filter=packages) or from those packages and all their subpackages (--auto_output_filter=subpackages). The flag --auto_output_filter=none means "don't filter anything", thus results in all warnings being printed (which is also Bazel's current default behavior). Output from failing commands will always be printed, no matter to which package it belongs. RELNOTES: Bazel now supports hiding compiler warnings for targets that you're not explicitly building (see https://docs.bazel.build/versions/master/user-manual.html#flag--auto_output_filter). PiperOrigin-RevId: 251419807
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.