Add `bazel mod show_repo --output=streamed_proto` and `--output=streamed_jsonproto` Serialize repo definitions to the same `Target` proto that `bazel query` uses. A few more notable details: * Add back `_original_name`, even to the Starlark output. This was removed in https://github.com/bazelbuild/bazel/pull/26493, but I believe it's still useful for debugging. * The output protos may contain a `$apparent_repo_name` or `$module_key` pseudo-attribute, which is the equivalent of the `## @repo_name` / `## module@version` line in the Starlark output. * Similar to the original Starlark output, the same (canonical) repo can be shown multiple times if the user explicitly specified the same repo in different ways: ```sh ❯ bazel-bin/src/bazel_nojdk mod show_repo @@rules_cc+ @rules_cc rules_cc ``` ```starlark ## @@rules_cc+: http_archive( name = "rules_cc+", ... ## @rules_cc: http_archive( name = "rules_cc+", ... ## rules_cc@0.2.9: http_archive( name = "rules_cc+", ... ``` ```sh ❯ bazel-bin/src/bazel_nojdk mod show_repo --output=streamed_jsonproto @@rules_cc+ @rules_cc rules_cc ``` ```js {"canonicalName":"rules_cc+", … {"canonicalName":"rules_cc+","apparentName":"@rules_cc", … {"canonicalName":"rules_cc+","moduleKey":"rules_cc@0.2.14", … ``` * Tighten up command argument validation so that `bazel mod show_{repo,extension} --output={graph,json}` now exits with an error, addressing a common source of user confusion. I decided not to add the same validation to all `bazel mod` subcommands since no one can possibly expect `bazel mod tidy --output=graph` to do something. Fixes #21617. Works towards #24692. Closes #27242. PiperOrigin-RevId: 843878072 Change-Id: I275ad2d3d24472a85d875176374d29bf42397d16
1 день назад История
README.md

Bazel

{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.

Getting Started

Documentation

Reporting a Vulnerability

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.

Contributing to Bazel

See CONTRIBUTING.md

Build status

Описание

a fast, scalable, multi-language and extensible build system

Конвейеры
0 успешных
0 с ошибкой