| commit | 451b816287accbc3c9953f8d83f1e7d723ea3a36 | [log] [tgz] |
|---|---|---|
| author | Googler <tanzhengwei@google.com> | Tue Jun 27 09:29:12 2023 -0700 |
| committer | fweikert <fwe@google.com> | Fri Jun 30 10:58:39 2023 +0200 |
| tree | ed479fc83d108abd8e9773401b2814daa9aa729b | |
| parent | fe6720b2eeb67d18beb9378e774bf2ef95ef85ea [diff] |
Automated rollback of commit 607d0f7335f95aa0ee236ba3c18ce2a232370cdb. *** Reason for rollback *** It changes the output format of --output=jsonproto to ndjson (i.e. which prints out ConfiguredTarget(s) and Configuration(s) separated by a newline) instead of being wrapped by a CqueryResult. Caught by https://github.com/bazelbuild/rules_go/issues/3597. *** Original change description *** Add new output format for cquery `--output=streamed_proto`. * The current state of the output formats of cquery has a few forms now: - (UNCHANGED) `cquery --output=proto|jsonproto|textproto --proto:include_configurations`: A single CqueryResult of the specified `--output` format. - (NEW) `cquery --output=streamed_proto --proto:include_configurations`: Multiple length-delimited `CqueryResult` protos each containing a single `ConfiguredTarget` or `Configuration`. - (UNCHANGED) `cquery --out... *** PiperOrigin-RevId: 543767534 Change-Id: Ib63ed4b5bc2b8e4823a4f935c1f7a32a22a80bcc
{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
