| commit | 3d60f1cf7aaacc98cf06f3c2eb62c2f521ce5868 | [log] [tgz] |
|---|---|---|
| author | Xudong Yang <wyverald@gmail.com> | Wed Nov 20 14:06:45 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Nov 20 14:07:54 2024 -0800 |
| tree | 41edd5c5744fb1c2febea71923ca8d0098d80e79 | |
| parent | 5e4a5dd1f7d91923f43096fd6bb5f55f0c34ec33 [diff] |
Allow any attributes on non-registry overrides So this kind of ran away from me... * The motivator for this PR was to allow any `http_archive` attributes to be specified on `archive_override`. It was kind of a design oversight that we didn't allow this, to be honest; we've slowly accumulated fixes like adding `init_gitsubmodules` to `git_override`, adding `patch_cmds` to `archive_override`, etc., but the better alternative is to just forward all kwargs to the actual underlying repo rule. * This somehow led to a big refactor where I remove the various `NonRegistryOverride` impls in favor of a simple wrapper around a `RepoSpec`, which led to the creation of a `RepoRuleId` class, which led to a refactor in BzlmodRepoRuleFunction (which also now houses the previous logic to validate labels in `ModuleFileGlobals`). * Also includes some random Java 21 fixes that I couldn't resist... (`ModuleOverride` is now a sealed interface; added several switch expressions) RELNOTES: `archive_override` now accepts all attributes usable with `http_archive`; similar for `git_override` and `git_repository`. Fixes https://github.com/bazelbuild/bazel/issues/24412 Closes #24378. PiperOrigin-RevId: 698515353 Change-Id: I285c382d10ef228d46a1f1d732daa77a21bf890b
{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
