Replace @ExecutionStrategy with module-based registration. Strategies and other action contexts used an annotation to indicate their identifying type (for example: "I'm something that can write a file for an action") and commandline identifiers (for example: "local", "remote"). This approach has a number of drawbacks: * Reflection is required to obtain the values, making it harder to understand control flow/dependencies. * Classes have to be created just so an annotation can be put upon them (everything else is handled as constructor parameters passed to a common base class). * Identifying information is not visible in places usually associated with configuration (Bazel modules) which merely register the class. This change removes the annotation-based propagation of identifying information and instead adds registration methods (called in Bazel modules that would previously simply register an annotation context instance) that take the data explicitly. RELNOTES: None PiperOrigin-RevId: 289881876
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only 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 solution. 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