commit | 1511dd208acc5c82f56b340044b54f35e7f32c0e | [log] [tgz] |
---|---|---|
author | mschaller <mschaller@google.com> | Mon Sep 21 14:19:33 2020 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Sep 21 14:20:38 2020 -0700 |
tree | 7e9fc17bd6d887f9480ae4359e33b9a81b87f7b6 | |
parent | 21a45079373275eccd37fd8200c04ed0c81c40d6 [diff] |
Equip LabelCause with DetailedExitCode, relay detailed input failures in action execution LabelCauses now specify a DetailedExitCode (like ActionFailed Causes). They're used during action execution to specify the cause of a missing input that fails the execution. MissingFileArtifactValue relays the DetailedExitCode describing why the file was missing. It no longer contains an exception. The exception was never used as an exception anyway (just as a bearer of a string). To be compatible with the required DetailedExitCode in LabelCauses, ToolchainExceptions now also specify detailed failures. RELNOTES: None. PiperOrigin-RevId: 332932518
{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