| commit | 0a1dce27650a233d8acb1f09a1181279f510cae8 | [log] [tgz] |
|---|---|---|
| author | Googler <pcloudy@google.com> | Thu Nov 02 07:04:09 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Nov 02 07:05:40 2023 -0700 |
| tree | 77834bd371b32a2732dc0fe4554df26baf035b27 | |
| parent | 7e1aac6e3fce17d6e7f174fe64a264ac61367578 [diff] |
Automated rollback of commit fc3460e92597091997fa4154173e2d4e973ede31. *** Reason for rollback *** Due to https://github.com/bazelbuild/bazel/issues/19749 *** Original change description *** Stablize and flip repository_cache_urls_as_default_canonical_id Introduced in #14268, this flag is very useful for bigger enterprise context where folks often version bumping dependencies without remembering to update the SHA256 of the downloaded file, leading to Bazel picking up older download entries from the repository cache. As we get more questions about this flag in Slack, marking it as stable and flip the default seems to be the r... *** RELNOTES: None PiperOrigin-RevId: 578840189 Change-Id: I390910b5dd838a4a1384c5d24cedde0b7c1b2b98
{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
