bazel analysis: don't use EvalException for non-Starlark errors StarlarkDefinedConfigTransition.evaluate and FunctionTransitionUtils.applyAndValidate now report errors through the event handler, instead of throwing EvalException. They use the new ValidationException class for internal plumbing of non-Starlark errors. This is another step towards eliminating the EvalException(Location) constructor. Also: - inline SDCT.evalFunction - tweak error messages PiperOrigin-RevId: 350775434
{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
