Bazel release 0.3.2

[katre]

Baseline will be 023a7bdc6506a23ff27ce392eb50d3927b3f409e Cherrypicks: bebbbe5d30f2a05e93780306208e1933d664d71b

[katre]

Command: ./scripts/release/release.sh create 0.3.2 023a7bdc6506a23ff27ce392eb50d3927b3f409e bebbbe5d30f2a05e93780306208e1933d664d71b

[katre]

Release 0.3.2 (2016-09-27)

Baseline: 023a7bd

Cherry picks:

• bebbbe5: Fix dependency on libtool's helper script make_hashed_objlist.py.

Incompatible changes:

• If you maintain a rule that uses persistent workers, you'll have to specify execution_requirements={"supports-workers": 1} in the ctx.action that intends to run a tool with workers. The WorkerSpawnStrategy will alert you with a warning message if you forget to make this change and fallback to non-worker based execution.
• It is now an error to include a precompiled library (.a, .lo, .so) in a cc_library which would generate a library with the same name (e.g., libfoo.so in cc_library foo) if that library also contains other linkable sources.
• The main repository's execution root is under the main repository's workspace name, not the source directory's basename. This shouldn't have any effect on most builds, but it's possible it could break someone doing weird things with paths in actions.
• Blaze doesn't support Unix domain sockets for communication between its client and server anymore. Therefore, the --command_port command line argument doesn't accept -1 as a valid value anymore.
• Skylark: It is an error to shadow a global variable with a local variable after the global has already been accessed in the function.
• bin_dir and genfiles_dir are now properties of ctx, not configuration. That is, to access the bin or genfiles directory from a Skylark rule, use ctx.bin_dir or ctx.genfiles_dir (not ctx.configuration.{bin,genfiles}_dir). At the moment, you can access {bin,genfiles}_dir from either, but the ctx.configuration version will stop working in a future release.
• filegroup-based C++ toolchains are not supported anymore. --*_crosstool_top options must always point to a cc_toolchain_suite rule (or an alias of one).
• repository_ctx.{download,download_and_extract,execute} API now use named parameters for optional parameters and no longer uses argument type to distinguished between arguments (executable attribute name must be specified when preceding optional arguments are missing).

New features:

• print and fail are now available in BUILD files.

Important changes:

• Add global hash() function for strings (only)
• Improve Android split transition handling.
• Removes exports_manifest attribute from android_binary rule.
• java_proto_library: control strict-deps through a rule-level and a package-level attribute.
• Persistent workers are now used by default for Java compilation in Bazel, which should speed up your Java builds by ~4x. You can switch back to the old behavior via --strategy=Javac=standalone. Check out http://www.bazel.io/blog/2015/12/10/java-workers.html for more details.
• objc_* rules can now depend on any target that returns an "objc" provider.
• Adds support for NDK12 to android_ndk_repository rule in Bazel.
• Test targets can disable the JUnit4 test security manager via a property.
• Disable the Android split transition if --android_cpu and fat_apk_cpu are both empty.
• New sandboxing implementation for Linux in which all actions run in a separate execroot that contains input files as symlinks back to the originals in the workspace. The running action now has read-write access to its execroot and /tmp only and can no longer write in arbitrary other places in the file system.
• Add worker support to single jar.
• Invoke source jar action as a worker.
• Sandboxed builds allow network access for builds by default. Tests will still be run without networking, unless "requires-network" is specified as a tag.
• Add path.realpath() method for Skylark repositories.
• On Mac devices, detect locally installed versions of xcode to:
  1. Use a sensible default if xcode is required but --xcode_version is unspecified.
  2. Use sensible default iOS SDK version for the targeted version of xcode if ios_sdk_version is unspecified.
• Emacs' [C-x `], a.k.a. next-error, works again in emacsen >= 25.1
• swift_library can be used to build watchOS apps.
• Exposes the is_device field on Apple platform objects and adds the apple_common.platform_type(name) method to retrieve a platform_type value that can be passed to methods like the Apple fragment's multi_arch_platform.
• Move Skylark git_repository rules to git.bzl
• Add support for aspects to attr.label() attributes
• Global varaiables HOST_CFG and DATA_CFG are deprecated in favor of strings "host" and "data. Argument cfg = "host" or cfg = "data" is mandatory if executable = True is provided for a label.
• The deprecation attribute of all rules now causes warnings to be printed when other targets depend on a target with that attribute set.
• Change default of --[no]instrument_test_targets to false, change default --instrumentation_filter (which previously tried to exclude test targets by heuristic) to only exclude targets in javatests.
• Remove deprecated absolute paths in blaze IDE artifacts
• When using android_binary.manifest_merger="android" the merger produces a summary log next to the merged manifest artifact.
• Allow different default mallocs per configuration.

[katre]

Adding cherrypick: 8a0d45ff940eea72a2887dc747d961c42f0e79c7

[kchodorow]

Could you modify the release notes to announce @bazel_tools//tools/build_defs/repo/git.bzl and @bazel_tools//tools/build_defs/repo/maven_rules.bzl?

[damienmg]

Marking as release blocker to find it :)

So another cherrypick to be added to the lot: c5545fd0896f3c602a9be0986debed6f0c9c662d

[meteorcloudy]

Please cherry-pick eb87208 c30432c They fix this important issue for Windows. #1847

[philwo]

Please cherry-pick:

sandbox: Replace the error-prone lazy cleanup of sandbox directories by a simple synchronous cleanup: https://github.com/bazelbuild/bazel/commit/95b16a89001014c48e77e5c38c4ca17bd28d3ebb

Fix #1849: Sandboxing on OS X should be turned off by default for 0.3.2: https://github.com/bazelbuild/bazel/commit/e898023ffc6c47a27312c4d3659dbeeccdb3cd37

Thanks!

[katre]

New RC pushed: ./scripts/release/release.sh create 0.3.2 \ 023a7bdc6506a23ff27ce392eb50d3927b3f409e \ bebbbe5 \ 8a0d45f \ 2bc0939 \ c5545fd \ eb87208 \ c30432c \ 95b16a8 \ e898023

[katre]

New and updated release notes: Incompatible changes:

• If you maintain a rule that uses persistent workers, you'll have to specify execution_requirements={"supports-workers": 1} in the ctx.action that intends to run a tool with workers. The WorkerSpawnStrategy will alert you with a warning message if you forget to make this change and fallback to non-worker based execution.
• It is now an error to include a precompiled library (.a, .lo, .so) in a cc_library which would generate a library with the same name (e.g., libfoo.so in cc_library foo) if that library also contains other linkable sources.
• The main repository's execution root is under the main repository's workspace name, not the source directory's basename. This shouldn't have any effect on most builds, but it's possible it could break someone doing weird things with paths in actions.
• Blaze doesn't support Unix domain sockets for communication between its client and server anymore. Therefore, the --command_port command line argument doesn't accept -1 as a valid value anymore.
• Skylark: It is an error to shadow a global variable with a local variable after the global has already been accessed in the function.
• bin_dir and genfiles_dir are now properties of ctx, not configuration. That is, to access the bin or genfiles directory from a Skylark rule, use ctx.bin_dir or ctx.genfiles_dir (not ctx.configuration.{bin,genfiles}_dir). At the moment, you can access {bin,genfiles}_dir from either, but the ctx.configuration version will stop working in a future release.
• filegroup-based C++ toolchains are not supported anymore. --*_crosstool_top options must always point to a cc_toolchain_suite rule (or an alias of one).
• repository_ctx.{download,download_and_extract,execute} API now use named parameters for optional parameters and no longer uses argument type to distinguished between arguments (executable attribute name must be specified when preceding optional arguments are missing).

New features:

• print and fail are now available in BUILD files.

Important changes:

• Added @bazel_tools//tools/build_defs/repo/git.bzl as a Skylark rule for Git repositories.
• Added @bazel_tools//tools/build_defs/repo/maven_rules.bzl as a Skylark rule for Maven repositories.
• Add global hash() function for strings (only)
• Improve Android split transition handling.
• Removes exports_manifest attribute from android_binary rule.
• java_proto_library: control strict-deps through a rule-level and a package-level attribute.
• Persistent workers are now used by default for Java compilation in Bazel, which should speed up your Java builds by ~4x. You can switch back to the old behavior via --strategy=Javac=standalone. Check out http://www.bazel.io/blog/2015/12/10/java-workers.html for more details.
• objc_* rules can now depend on any target that returns an "objc" provider.
• Adds support for NDK12 to android_ndk_repository rule in Bazel.
• Test targets can disable the JUnit4 test security manager via a property.
• Disable the Android split transition if --android_cpu and fat_apk_cpu are both empty.
• New sandboxing implementation for Linux in which all actions run in a separate execroot that contains input files as symlinks back to the originals in the workspace. The running action now has read-write access to its execroot and /tmp only and can no longer write in arbitrary other places in the file system.
• Add worker support to single jar.
• Invoke source jar action as a worker.
• Sandboxed builds allow network access for builds by default. Tests will still be run without networking, unless "requires-network" is specified as a tag.
• Add path.realpath() method for Skylark repositories.
• On Mac devices, detect locally installed versions of xcode to:
  1. Use a sensible default if xcode is required but --xcode_version is unspecified.
  2. Use sensible default iOS SDK version for the targeted version of xcode if ios_sdk_version is unspecified.
• Emacs' [C-x `], a.k.a. next-error, works again in emacsen >= 25.1
• swift_library can be used to build watchOS apps.
• Exposes the is_device field on Apple platform objects and adds the apple_common.platform_type(name) method to retrieve a platform_type value that can be passed to methods like the Apple fragment's multi_arch_platform.
• Move Skylark git_repository rules to git.bzl
• Add support for aspects to attr.label() attributes
• Global varaiables HOST_CFG and DATA_CFG are deprecated in favor of strings "host" and "data. Argument cfg = "host" or cfg = "data" is mandatory if executable = True is provided for a label.
• The deprecation attribute of all rules now causes warnings to be printed when other targets depend on a target with that attribute set.
• Change default of --[no]instrument_test_targets to false, change default --instrumentation_filter (which previously tried to exclude test targets by heuristic) to only exclude targets in javatests.
• Remove deprecated absolute paths in blaze IDE artifacts
• When using android_binary.manifest_merger="android" the merger produces a summary log next to the merged manifest artifact.
• Allow different default mallocs per configuration.

[abergmeier-dsfishlabs]

Would be good to have #1877 before releasing 0.3.2 into the wild.

[katre]

Documentation is not synced with releases, so #1877 is independent of the 0.3.2 release.

[damienmg]

We are blocker free now and we need to release by tomorrow.

@meteorcloudy wants a change for windows in, but we are waiting for ci to vet it. I say we emit a new canary tonigh with it and release tomorrow :)

[katre]

@meteorcloudy Can you link the issue here so we can track it?

[damienmg]

the commit is ffdc05d2278d7f9c6e299c923019f689cde5fe76, it is being vetted by ci.bazel.io

[meteorcloudy]

Thanks, Damien. @katre There is no issue for this commit, please just cherry-pick it.

[katre]

Regenerated the release candidate: $ ./scripts/release/release.sh create 0.3.2 \ 023a7bd \ bebbbe5 \ 8a0d45f \ 2bc0939 \ c5545fd \ eb87208 \ c30432c \ 95b16a8 \ e898023 \ ffdc05d

And pushed it. Change notes are the same.

[petemounce]

I'm not familiar with the bazel release process. Is there a thing that I can subscribe to so I'm notified of new releases?

[katre]

Release candidates and releases are emailed to bazel-discuss+release-candidate@googlegroups.com as they are created.

I'm trying to release 0.3.2 now, so if you subscribe quickly you'll see one soon, hopefully.

[damienmg]

Also for full release they appear in https://github/bazelbuild/bazel/releases

On Fri, Oct 7, 2016 at 5:13 PM katre notifications@github.com wrote:

Release candidates and releases are emailed to bazel-discuss+release-candidate@googlegroups.com as they are created.

I'm trying to release 0.3.2 now, so if you subscribe quickly you'll see one soon, hopefully.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/bazelbuild/bazel/issues/1840#issuecomment-252279191, or mute the thread https://github.com/notifications/unsubscribe-auth/ADjHf3U7EUrvnbp7bzgwOzNdDpi7tScmks5qxmGogaJpZM4KH1Jc .

[petemounce]

@katre thanks; subscribed.

@damienmg that's where I've been polling; I was hoping for something that would push to me.

[katre]

0.3.2 release is finished.