| commit | 2acd34ba7a7b5e7275590f325c5b9a86321c8460 | [log] [tgz] |
|---|---|---|
| author | Googler <tjgq@google.com> | Thu Jul 04 05:17:51 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jul 04 05:19:19 2024 -0700 |
| tree | 0a8715ef6f1accdf255e47d03d55c4c5ce5bd8ba | |
| parent | 6e2e3a169cb3ba6e37499ccc752f6375848df275 [diff] |
Clarify the role of the WorkResponse.output field. The documentation suggests that the stdout/stderr of a work unit may be sent to the stderr of the worker process, but this will fail to ascribe the output to a particular action; instead it will be collected in a per-worker log file [1][2]. In contrast, the WorkResponse.output field is copied to the action stderr [3]. [1] https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/worker/SingleplexWorker.java;l=111;drc=290315e048b94c351f2fa23bfef2a164b6f78268 [2] https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/worker/WorkerMultiplexer.java;l=203;drc=0b280ac442aa51c7cca1c311658dbd1a6346dff5 [3] https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/worker/WorkerSpawnRunner.java;l=214;drc=e3aae6ca8bba30561b01b2727bcffca8b74638cc PiperOrigin-RevId: 649380094 Change-Id: I22209f14cfe69660aeaa2a8f53b8086df8bd1e30
{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
