commit | 0d14ec84a06c4da628a7f6d9d1c5f9314392ab15 | [log] [tgz] |
---|---|---|
author | Bazel Release System <noreply@google.com> | Tue Oct 20 09:22:23 2020 -0400 |
committer | John Cater <jcater@google.com> | Tue Oct 20 09:22:23 2020 -0400 |
tree | 855621dd55d01e9dd47da8740cb688575877ff51 | |
parent | a991db7c2f66a354666388d888dcef9b0d0f70c0 [diff] |
Release 3.7.0 (2020-10-20) Baseline: a991db7c2f66a354666388d888dcef9b0d0f70c0 Incompatible changes: - The syntax //foo/BUILD can no longer be used on the command line to refer to the //foo:BUILD target. Use //foo:BUILD (preferred) or foo/BUILD instead. This does not affect BUILD/bzl files, where that syntax already didn't work. - This removes `--objc_header_scanner_tool`. The flag was primarily used internally, and to our knowledge, a compatible tool was never released. Therefore this flag is believed to be unused. New features: - select() directly supports constraint_value (no need for an intermediate config_setting). Important changes: - Non-android targets can again be built when android_sdk_repository is present but invalid. - Add a build variable for -install_name / -soname. - Add a build variable for -install_name / -soname. - Include "resources" attr in dependency attributes for java_* coverage configuration. - --trim_test_configuration should work for almost all cases when a non-test target depends on a test. - Javac now supports multiplex workers. - Javac now supports multiplex workers. - Blaze now allows symbolic links that point to their own ancestor unless they are traversed recursively by e.g. a //... recursive target pattern or a recursive glob. - Blaze now allows symbolic links that point to their own ancestor unless they are traversed recursively by e.g. a //... recursive target pattern or a recursive glob. - Blaze now allows symbolic links that point to their own ancestor unless they are traversed recursively by e.g. a //... recursive target pattern or a recursive glob. - Generated Go protobufs no longer depend on //net/proto2/go:proto This release contains contributions from many people at Google, as well as Benjamin Peterson, Cristian Hancila, Ed Schouten, Fredrik Medley, Greg Estren, jgehw, Jin, Kalle Johansson, Keith Smiley, Kseniia Vasilchuk, Michael Eisel, Michael Hackner, Michael Krasnyk, Mostyn Bramley-Moore, Ruixin Bao, Samuel Giddins, Simon Stewart, Torgil Svensson, Ulf Adams, Vasilios Pantazopoulos, Wenyu Zhang, Yannic Bonenberger, yoav-steinberg.
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only 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