commit | 09d50f9b6186a9901d9d2cc3a9cbc242eb8798f0 | [log] [tgz] |
---|---|---|
author | Xdng Yng <wyverald@gmail.com> | Fri Apr 19 10:46:39 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Apr 19 10:48:25 2024 -0700 |
tree | cb80bd2e0595478048bf6702c4c0c3d4e6939025 | |
parent | 128c8635150d13a37e930fe1b94be96d9c42acff [diff] |
Add new flag `--incompatible_disable_native_repo_rules` This new flag defaults to `false`. When set to `true`, native repo rules cannot be used in WORKSPACE; their Starlark counterparts must be used. Native repo rules already can't be used in Bzlmod. Work towards https://github.com/bazelbuild/bazel/issues/18285. Closes #21913. PiperOrigin-RevId: 626410163 Change-Id: I4981cd8d99fc87d0d0b66991e563941478b40f12
{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