| commit | 1d2fb1ffb09bb58a3a697ef730c5e41de3ed258a | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Thu Dec 22 13:30:46 2016 +0100 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Thu Dec 22 13:30:46 2016 +0100 |
| tree | 2f707f7a4b480e1c86d98c960cb295b3d1a52930 | |
| parent | 669e13f5459ffd0228f901e4485412fd139c50ed [diff] |
Release 0.4.3 (2016-12-22)
Baseline: c645a45
Cherry picks:
+ af878d0: Add coverage support for java test. (series 4/4 of
open-sourcing coverage command for java test)
+ 09b92a8: Rollback of commit
67b4d5250edcefa7220e928e529b1f385e2dc464.
+ b11dd48: Fix bad bug with the parallel implementation of
BinaryOperatorExpression. Turns out that
ForkJoinTask#adapt(Callable) returns a ForkJoinTask
whose Future#get on error throws a ExecutionException
wrapping a RuntimeException wrapping the thrown checked
exception from the callable. This is documented
behavior [1] that I incorrectly didn't know about.
+ 9012bf1: Fix scripts/packages/convert_changelog to read the
changelog correctly
+ 55c97bc: Release script: if master branch does not exist, fall
back on origin/master
+ 4fb378c: Debian repository: override section and priority fields
+ acbcbc2: Fix release notes in emails
+ 4975760: Fix PathFragment to not use Java8-only static hashCode
methods.
+ 05fd076: Disable sandboxing for XibCompile actions.
Incompatible changes:
- Skylark maven_jar and maven_aar settings attribute is now a label
so it can be checked into your workspace.
- --{no}experimental_use_rclass_generator is now a nop.
New features:
- Coverage support (*experimental*) for pure Java target.
Use `bazel coverage //my:target` to generate coverage information
from a `java_test`.
Important changes:
- Enable fallback URLs in Skylark http rules.
- cc_proto_library generates C++ code from proto_library rules.
- cc_library now supports the strip_prefix and strip_include_prefix
attributes for control of include paths.
- Skylark dicts internally don't rely on keys order anymore and
accept any hashable values (i.e. structs with immutable values)
as keys. Iteration order of dictionaries is no longer specified.
{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.