Add no-remote-cache and no-remote-exec execution requirements This resolves https://github.com/bazelbuild/bazel/issues/7932 It introduces two new execution requirements: - `no-remote-exec`: disallows remote execution without preventing remote caching - `no-remote-cache`: disallows remote caching without preventing remote execution or local caching The current behavior of `no-remote` and `no-cache` remain unchanged. Closes #8710. PiperOrigin-RevId: 259901280
{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 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
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.