| commit | a1699bd77f1770670eac191d701757b98556b1c5 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Wed Oct 26 09:29:48 2016 -0400 |
| committer | Kristina Chodorow <kchodorow@google.com> | Wed Oct 26 09:29:48 2016 -0400 |
| tree | 82dae1d8328d5249333172e31f98f30fdda2cd50 | |
| parent | e03b5484c5a79783cc1935d4af81d61f24efbdc5 [diff] |
Release 0.4.0 (2016-10-26)
Baseline: 088bbc6
Cherry picks:
+ b01160c: Stamp Windows release.
+ 2d6736e: Add --no-tty for gpg signing
+ 9b1dfb8: Remove .sig file before gpg signing
+ 81aede1: Reimplement whole archive on Windows
Incompatible changes:
- Skylark: updating list/dicts while they are being looped over is not
allowed. Use an explicit copy if needed ("for x in list(mylist):").
- Bazel now uses the --cpu flag to look up Jvms; it falls back
to "default" if it can't find a Jvm matching the CPU value.
- --command_port=-1 to use AF_UNIX for client/server communications
is not supported anymore.
- Sandboxed actions can access the network by default, unless their
target has a "block-network" tag.
New features:
- Files now have an "extension" property in Skylark.
Important changes:
- Added a new flag --sandbox_tmpfs_path, which asks the sandbox to
mount an empty, writable directory at a specified path when
running actions. (Supported on Linux only for now.)
- Update protoc-3.0.0-mingw.exe to a working (statically linked)
binary
- apple_static_library rule to create multi-architecture static
archive files from Objc/C++/Swift dependencies on apple platforms
- JS: Add support for localization with closure managed rules.
- Create a flag --android_dynamic_mode to turn off dynamic mode
during the Android split transition.
- Darwin sandboxing is default.
- Remove flag --experimental_zip_tree_artifact from j2objc Java
annotation processing support.
- A few functions are added to BUILD files for consistency (hash,
dir,
hasattr, getattr) with .bzl files, although they are not very
useful.
- --watchfs is now a command option; the startup option of the same
name is deprecated. I.e., use bazel build --watchfs, not
blaze --watchfs
build.
{Fast, Correct} - Choose two
Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:
A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.
An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.
Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.
Find more background about Bazel in our FAQ.