| commit | 5c9fcaf279f3912d1cd117fed4eeaf977b10644f | [log] [tgz] |
|---|---|---|
| author | Irina Iancu <elenairina@google.com> | Thu Nov 24 16:23:50 2016 +0000 |
| committer | Dmitry Lomov <dslomov@google.com> | Fri Nov 25 12:20:21 2016 +0000 |
| tree | cde0c36c286c99b9661f0a53306e0a2bcf259cc2 | |
| parent | bfa166b8964c3e72e84293231ad5e24d1c31d3bb [diff] |
Introducing the Java compilation black box in Skylark. Adding a new declared provider that will be the returning value of the Java compilation method in Skylark. This provider is considered a black-box from Skylark and it should only be passed around (returned from a rule/aspect implementation) to allow Java rules to depend on it. Also adding a new Skylark module (java_common) to allow retrieving the Java dependencies' black-box from Skylark implementations. -- MOS_MIGRATED_REVID=140138446
{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.