| commit | a6a5176f44e59f64fc0ec9acb555e3b214ce7633 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Thu Feb 17 19:54:47 2022 +0100 |
| committer | fweikert <fwe@google.com> | Thu Feb 17 19:54:47 2022 +0100 |
| tree | a909dae8ff426f06b509db97ff64028c4b287b2d | |
| parent | 9f549dc5e982a11ab967b3d601ba62cde95461c5 [diff] |
Release 6.0.0-pre.20220208.2 (2022-02-17)
Baseline: de3c14da9eba34bed39f4cb34446037813420ae3
Cherry picks:
+ a6bfab095ff11cc9d37e45994c2dd85be626710f:
Automated rollback of commit
64ac2a81f73ba7b085d0de65f12230814f4151c8.
Important changes:
- Tests that fail to create or complete their
`TestAttemptContinuation` by
throwing an `ExecException` will report an `INCOMPLETE` status.
Previously, Bazel
would fail to report any status for the test attempt.
This release contains contributions from many people at Google, as well as divanorama, Fabian Meumertzheim, Keith Smiley, Marek uppa, Niyas Sait, Thi Doan, Yesudeep Mangalapilly.
{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
