| commit | 490b0956e6cc8449072f3010c5197d9d6c621d09 | [log] [tgz] |
|---|---|---|
| author | gregce <gregce@google.com> | Thu Jul 06 18:44:38 2017 -0400 |
| committer | John Cater <jcater@google.com> | Fri Jul 07 07:08:19 2017 -0400 |
| tree | 93e46e560d7ba8cb974e2a87124282056a9e5ff5 | |
| parent | 5ba65a5c00f18a5ebd677ce10693b453736915f9 [diff] |
Factor out BuildConfigurationCollection.Transitions.getDynamicTransition. This is a legacy dependency on the configuration transition table, which is only needed for static configurations. Dynamic configurations didn't actually use anything in that table: this was just a convenience interface that could have equally been defined somewhere else. So this cl defines it somewhere else. There's still one last dependency: Transitions.configurationHook. We'll tackle that in a followup cl. PiperOrigin-RevId: 161141650
{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.