| commit | 8a81b81eff96b55b512ff2fdf7129184f271453f | [log] [tgz] |
|---|---|---|
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | Mon May 06 15:00:56 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon May 06 15:02:32 2024 -0700 |
| tree | b4d90e023e00ac37cba1b71bf65c6de82094ae9e | |
| parent | c9117afe7da0d55f261fe204d49b2535b1a2c6ca [diff] |
Store remote registry file hashes in the lockfile `MODULE.bazel`, `bazel_registry.json` and `source.json` files obtained from remote registries are stored in the repository cache and their hashes are collected in the lockfile. This speeds up incremental module resolutions, such as after adding a new `bazel_dep`. Yanked versions are not stored in the lockfile. Their handling will be part of a follow-up PR. Implements part of https://docs.google.com/document/d/1TjA7-M5njkI1F38IC0pm305S9EOmxcUwaCIvaSmansg/edit Work towards #20369 Closes #21901. PiperOrigin-RevId: 631195852 Change-Id: I35c30af7f9c3626bdbcb04c85b8c2502eeaafd3e
{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
