| commit | 5a77623179445f22a3d6daf92669ddcfe0fd4c68 | [log] [tgz] |
|---|---|---|
| author | Lukacs Berki <lberki@google.com> | Mon May 23 08:07:01 2016 +0000 |
| committer | Yue Gan <yueg@google.com> | Mon May 23 08:26:03 2016 +0000 |
| tree | 3f652c4337010e717caeffa1480d4e5b3e96499e | |
| parent | d91d047da35511487c4fcce6f5e438ba779a668b [diff] |
Make alias targets keep their own configuration. This prevents the case of a rule acquiring the null configuration in case the alias points to an input file. Which, in turn, makes "bazel build" work for these targets. The reason it breaks is that TargetCompletionValue instances are created from the associated ConfiguredTarget in SkyframeExecutor#buildArtifacts(), which means that if the configurations do not match, TargetCompletionFunction requests a different ConfiguredTargetValue than it was created from. Fixes #1297. -- MOS_MIGRATED_REVID=122973526
{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.