commit | 2e62fe7a8609160f545ece1e72a78cca3791a647 | [log] [tgz] |
---|---|---|
author | Googler <jhorvitz@google.com> | Tue Nov 28 12:54:07 2023 -0800 |
committer | fweikert <fwe@google.com> | Wed Dec 06 23:12:05 2023 +0100 |
tree | 8afd8cb344060318c0a6b0e5345a0d9af9cf32bb | |
parent | 4a29f0851d1cde0240793cdc7a2e2cab926d31b7 [diff] |
Automated rollback of commit 353000ebc512e4f1654d123713b003011751e07e. *** Reason for rollback *** b/312694497 *** Original change description *** Make the BesUploadMode per transport instead of per invocation. As a result, `--build_event_[text|json|binary]_file_upload_mode` are introduced to set the upload mode for build event file respectively. The default value for them is `wait_for_upload_complete`. The implicit requirement on `--bes_upload_mode=wait_for_upload_complete` is also removed. Alternate to https://github.com/bazelbuild/bazel/pull/19322. PiperOrigin-RevId: 586076379 Change-Id: I020c969497fcf72fe77754a5438ff5353ab606cb
{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