Use failure details in InfoCommand, InvalidConfigurationException Adapts its usage of ExitCode and AbruptExitException to add FailureDetail values. Failure modes detected there now have corresponding codes in failure_details.proto. InvalidConfigurationException now specifies a fine-grained code to more precisely represent what configuration-related activity failed. This gets its first use for platform mapping failures. (Platform mapping failures may benefit from additional refinement.) RELNOTES: None. PiperOrigin-RevId: 309104771
{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
