| commit | 44dd226a540ace2ef1c348f778512616de82ce31 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Mon Jun 19 15:31:04 2017 -0400 |
| committer | Kristina Chodorow <kchodorow@google.com> | Tue Jun 20 14:35:19 2017 -0400 |
| tree | 909efeb0c6722e5a0917a7459bca58392b302c7e | |
| parent | 42b2c9ab57c8e593623138f414b55bcc2339f64d [diff] |
Create a general WrappingProvider concept and use for java_proto_library and friends. The wrapping provider contains its own provider map containing any providers that may conflict. This can be used generally for any aspect that wants to override its base providers (during migration), and due to the generality we should be able to cut down on code size and complexity. Once we have this, we can more easily and uniformly bind aspects to Skylark for aspect-on-aspect functionality. The Skylark providers can be instantiated with a wrapping provider if one is present, or fall through to the base target if they aren't. We will also likely save a bit of memory from cutting down on wrapping classes. PiperOrigin-RevId: 159461325
{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.