| commit | 7bdc69cff348f8c1d4c1f816507a4221d4349538 | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Mon Jan 09 21:17:31 2017 +0000 |
| committer | Marcel Hlopko <hlopko@google.com> | Tue Jan 10 10:22:50 2017 +0000 |
| tree | 25d9592897162b4b18fb2e46a5b7d83e795a4236 | |
| parent | e7fd53927df37a55cf5a4337fabced828cda8109 [diff] |
Skylark repository invalidation design doc update 1. Set status to implementing 2. Reorder the list of tasks because we need to invalidate correctly Skylark repositories before enabling environ parameter. 3. Fix the step 2 (was step 3) in order to pass a map instead of creating a new function. -- Change-Id: I9387ccedf75d63fef7e2e9546dc1f0421cb12679 Reviewed-on: https://cr.bazel.build/7972 PiperOrigin-RevId: 143999391 MOS_MIGRATED_REVID=143999391
{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.