| commit | c553e35976582ca861040dac3af12c5ed9f11ede | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Fri Jan 15 13:55:37 2016 +0100 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Fri Jan 15 13:55:37 2016 +0100 |
| tree | de92907f6c1e8db37f0c5fc47ec48ace6682934c | |
| parent | 9dc1f5acc3a90b4998e4982b21ff9b7a9984c463 [diff] |
Release 0.1.4 (2016-01-15)
Baseline: e933d5e
+ 3d796fe: Rollback of commit
ac6ed79e1a3fa6b0ca91657b28e2a35f7e49758c.
+ 7a02e5d: Fix installer under OS X
+ 848740c: Fix bazel version for debian package
+ 7751d43: Add a method for getting the root of a rule workspace
to the Label method
Important changes:
- add loadfiles() query operator, to find skylark files loaded by
targets.
- Added ability to declare and use aspects in Skylark.
- Skylark load statements may now reference .bzl files via build
labels, in addition to paths. In particular, such labels can be
used to reference Skylark files in external repositories; e.g.,
load("@my_external_repo//some_pkg:some_file.bzl", ...).
Path-based loads are now deprecated and may be disabled in the
future. Caveats: Skylark files currently do not respect package
visibility; i.e., all Skylark files are effectively public. Also,
loads may not reference the special //external package.
- Relative paths can now be used for 'path' with
new_local_repository and local_repository.
{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.