| commit | 91ad91d5be3def4ffe4081174a87a307b63d03ad | [log] [tgz] |
|---|---|---|
| author | Googler <adgar@google.com> | Tue Nov 21 14:13:43 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Nov 21 14:15:09 2023 -0800 |
| tree | fc73981dadef57760dbb0dddf37e56e3a2b5d65f | |
| parent | 2ceb1326a576699faa3bd679cfb646feb2352c89 [diff] |
Add `CommandExtensionReporter` to `CommandEnvironment` to enable streaming back command extension messages. The `RunResponse.command_extensions` field is currently populated at the end of a command. Since `Run` is a streaming operation we can conceivably stream back command extensions if the build tool were given an appropriate interface to do so. The normal Bazel client (the C++ binary) will currently drop these extensions on the floor so users will need to connect directly to the Bazel server to retain the structured metadata returned in command extensions. A possible enhancement would extend the C++ client to optionally write response extensions to a file or files. PiperOrigin-RevId: 584426022 Change-Id: Ie0c894d09ac8b2ddd1b1419396ac292a61b1af77
{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
