| commit | 61fa9331099dbc73df4b9d51ad1143f23369d8a2 | [log] [tgz] |
|---|---|---|
| author | Tiago Quelhas <tjgq@google.com> | Thu Nov 16 16:35:38 2023 +0100 |
| committer | GitHub <noreply@github.com> | Thu Nov 16 15:35:38 2023 +0000 |
| tree | 5b17dff13a29f135994e7161b7d766f42ddb95b7 | |
| parent | 97f8e5c7f173fbd5fbb64ffa6392187b8f52729c [diff] |
[7.0.0] Forbid simultaneously requesting both a JSON and binary execution log. (#20222) Although this is a breaking change, I find it unlikely that anyone requests both, given how unwieldy these files are. This avoids future complexity around format conversions as we add more of them (specifically: in order to add a new format while keeping the old formats equally performant, the choice of "raw" format would likely have to vary, so there would be additional pairs to convert between). The current conversion code can also be simplified, as there's now at most one conversion to make, but I prefer doing that separately. Related to https://github.com/bazelbuild/bazel/issues/18643. PiperOrigin-RevId: 582994996 Change-Id: I8e0bc228c73a0da7f3e7b830ade2cab6c14319ff
{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
