| commit | d3d62d9b96f76c59d8a61b60a89306a4ca5479be | [log] [tgz] |
|---|---|---|
| author | Ian (Hee) Cha <heec@google.com> | Thu Jul 20 10:20:14 2023 -0700 |
| committer | GitHub <noreply@github.com> | Thu Jul 20 17:20:14 2023 +0000 |
| tree | 861fcdb2a8f8105d1fe5f1cfcc64fbb5e7ea94ff | |
| parent | 762c470f2be26237b68a7afa69dc90f64ea3fed8 [diff] |
Add support for isolated extension usages to the lockfile (#19008) Previously, Bazel would crash if a module declares an isolated extension usage and the lockfile is used. Closes #18991. PiperOrigin-RevId: 549631385 Change-Id: Id8e706991dc5053b2873847a62f5e0b777347c69 Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>
{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
