Document `--build_request_id` (https://github.com/bazelbuild/bazel/pull/30805) ### Description Documents `--build_request_id`, covering it's intended purpose and where the value is used. `OptionDocumentationCategory.UNCATEGORIZED` used as no other more suitable currently documentation category exists. ### Motivation To address a documentation gap currently poorly covered by: - https://github.com/bazelbuild/bazel/issues/15036#issuecomment-1073072405 - https://github.com/buildbarn/bb-remote-execution/blob/13313e6ab05b00769af48cf5d6e4926ce15b1f2b/pkg/proto/configuration/scheduler/scheduler.proto#L144-L149 - https://www.hermetiq.com/docs/configuration#:~:text=build%20%2F%2F%2E%2E%2E-,%2D%2Dbuild%5Frequest%5Fid - https://github.com/buildfarm/buildfarm/blob/6fdea379a455a579bf582eff1acef001769a769d/_site/docs/execution/observability.md?plain=1#L22 ### Build API Changes No ### Checklist - [x] I have added tests for the new use cases (if any). - [x] I have updated the documentation (if applicable). ### Release Notes RELNOTES: None Closes #30805. PiperOrigin-RevId: 970357795 Change-Id: I348a1b0e5addf9bee3544d2af1b8be4c26114869
{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.
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