| commit | b89978317cf14a7f3d24616a3bf66e79bccb2482 | [log] [tgz] |
|---|---|---|
| author | Googler <chiwang@google.com> | Thu Sep 05 05:27:57 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Sep 05 05:29:53 2024 -0700 |
| tree | 53a38c3df303301a8af99a0b0b95e3db3659846d | |
| parent | 6c31f6905ded5321301cb14a615b96a66f2e4e63 [diff] |
Automated rollback of commit 3e464fcd3be4a7866719a6e1ecc2480a3361e441. *** Reason for rollback *** Users might use a HTTP connection to a real remote cache, e.g.https://github.com/bazelbuild/bazel/issues/18696#issuecomment-2331162637. *** Original change description *** Disable BwoB if using HTTP cache. HTTP cache is generally configured to automatically delete old files. It doesn't support lease extension and doesn't understand the relationships between AC and CAS. Hence, they are incompatible. Fixes #18696. RELNOTES: Build without the Bytes is disabled when using HTTP cache. PiperOrigin-RevId: 671334333 Change-Id: I16e3ab50726b7ff2c81eeabc0670b57b581ce2e2
{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:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
