| commit | 585d1a09fdd7e24e9fca4ebb8fefa172e44599f3 | [log] [tgz] |
|---|---|---|
| author | John Field <jfield@google.com> | Wed Dec 16 16:03:52 2015 +0000 |
| committer | Nathan Harmata <nharmata@google.com> | Wed Dec 16 20:23:32 2015 +0000 |
| tree | b51db0f97182fcb61e271af689a6e36d49017a64 | |
| parent | 5f909179f35f97841580f6566caf8a0cf1a0bdba [diff] |
Move annotation classes used for referencing framework Java classes from Skylark into their own package. This allows, e.g., classes in the syntax package to access classes in the cmdline package without creating circular dependencies. While we're here: - Removed a couple of unused BUILD deps flagged in []. - Updated SkylarkRuleImplementationFunctionsTest to remove non-ASCII characters and clarify the intent of the test. -- MOS_MIGRATED_REVID=110360763
{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.