Release 0.29.0rc2 (2019-08-02)
Baseline: 6c5ef5369a3ffceb8a65cc159a2fff1401242810
Important changes:
- rule_test: fix Bazel 0.27 regression ("tags" attribute was ingored, https://github.com/bazelbuild/bazel/issues/8723
- Adds --incompatible_enable_execution_transition, which enables incremental migration of host attributes to exec attributes.
- objc_proto_library rule has been deleted from Bazel.
- repository_ctx.read is no longer restricted to files in the repository contructed.
- tags 'no-remote', 'no-cache', 'no-remote-cache', 'no-remote-exec', 'no-sandbox' are propagated now to the actions from targets when '--ncompatible_allow_tags_propagation' flag set to true. See #8830.
- Adds flag --//tools/build_defs/pkg:incompatible_no_build_defs_pkg. This flag turns off the rules //tools/build_defs/pkg:{pkg_deb, pkg_rpm, pkg_tar}.
- The Android NDK is now integrated with toolchains. To use them, pass the
--extra_toolchains=@androidndk//:all flag or register them in your WORKSPACE with register_toolchains("@androidndk//:all").
- Stdout and stderr are checked to determine if output is going to a terminal.
--is_stderr_atty is deprecated and --isatty is undeprecated.
- --incompatible_load_proto_rules_from_bzl was added to forbid loading the native proto rules directly. See more on tracking issue #8922
- Docker Sandbox now respects remote_default_platform_properties
- pkg_deb, pkg_rpm & pkg_tar deprecation plan announced in the documentation.
- The new java_tools release:
- fixes https://github.com/bazelbuild/bazel/issues/8614
- exposes a new toolchain
@java_tools//:prebuilt_toolchain which is using all the pre-built tools, including singlejar and ijar, even on remote execution. This toolchain should be used only when host and execution platform are the same, otherwise the binaries will not work on the execution platform.
- java_common.compile supports specifying annotation_processor_additional_inputs and annotation_processor_additional_outputs for the Java compilation action for supporting annotation processors that consume or produce artifacts. Fixes #6415
- There is now documentation on optimizing Android app build performance. Read it at https://docs.bazel.build/versions/0.29.0/android-build-performance .html
- Execution log now respects --remote_default_platform_properties
- Include a link to the relevant documenation on transitive Python version errors.
- New incompatible flag --incompatible_disable_target_provider_fields removes the ability (in Starlark) to access a target's providers via the field syntax (for example,
ctx.attr.dep.my_provider). The provider-key syntax should be used instead (for example, ctx.attr.dep[MyProvider]). See https://github.com/bazelbuild/bazel/issues/9014 for details.
- A new platform exec_properties is added to replace remote_execution_properties.
- Added --incompatible_load_python_rules_from_bzl, which will be flipped in Bazel 1.0. See https://github.com/bazelbuild/bazel/issues/9006.
- add --break_build_on_parallel_dex2oat_failure to shortcut tests on dex2oat errors
This release contains contributions from many people at Google, as well as Alexander Ilyin, Arek Sredzki, Artem Zinnatullin, Benjamin Peterson, Fan Wu, John Millikin, Loo Rong Jie, Marwan Tammam, Oscar Bonilla, Peter Mounce, Sergio Rodriguez Orellana, Takeo Sawada, and Yannic Bonenberger.
Notice: Bazel installers contain binaries licensed under the GPLv2 with Classpath exception. Those installers should always be redistributed along with the source code.
Some versions of Bazel contain a bundled version of OpenJDK. The license of the bundled OpenJDK and other open-source components can be displayed by running the command bazel license. The vendor and version information of the bundled OpenJDK can be displayed by running the command bazel info java-runtime. The binaries and source-code of the bundled OpenJDK can be downloaded from our mirror server.
Security: All our binaries are signed with our public key 48457EE0.
Index of files