| commit | bb3f3299e1c9cdab39aa70c1c773de4f630c57b5 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Wed Sep 25 13:43:58 2024 -0700 |
| committer | keertk <keerthanakumar@google.com> | Wed Oct 02 18:36:33 2024 +0000 |
| tree | c0f98c983093fe999186f8af0b3990f99d8c71b3 | |
| parent | f4d92d45be3617b72c21ad5ce8912fa548472e50 [diff] |
Automated rollback of commit 4607ad439fe8869c8e8951d953e2d3adb613e6d6. *** Reason for rollback *** [] *** Original change description *** Automated rollback of commit 76b42af100b0a1079a25a7ba24bffcd6bc53f6e0. *** Reason for rollback *** The internal tests were fixed. *** Original change description *** Automated rollback of commit 750f0a1c05f56403e3b4a3d08b6d7de6ce3ed7f7. *** Reason for rollback *** This CL breaks internal tests. *** Original change description *** Fix `_validation` output group merging While https://github.com/bazelbuild/bazel/commit/cd725834eba3edb53b7a7dd9867363ef1fe00e57 made it so that a rul... *** PiperOrigin-RevId: 678831804 Change-Id: I7725ff31af4c184c79162249283018d808b6b41e
{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
