commit | 8529746358ff5d88dc7ddf584a85ba0aa1a269a8 | [log] [tgz] |
---|---|---|
author | gregce <gregce@google.com> | Fri Aug 18 21:20:29 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Mon Aug 21 14:15:59 2017 +0200 |
tree | 5aa2c9f9e6f22b37d4d1c320d21fa4436545051b | |
parent | 8158a286a8e72ec3f5259d155f6856fea9d07fea [diff] |
Replace TransitionApplier interface with a dedicated class. This accomplishes a few goals: 1. Removes the outdated BuildConfiguration.StaticConfigurationApplier code. 2. Removes the TransitionApplier abstraction completely. This was an awkward bridge meant to support both static and dynamic implementations. 3. Moves transition logic to its own dedicated class: ConfigurationResolver. This no longer belongs in BuildConfiguration, which we ultimately want to become a simple <key, value> map. Part of the static config cleanup effort. PiperOrigin-RevId: 165736955
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase and Continuous Integration system. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.