| commit | 7ffa88f56f96abb7be826ff34045919119a7db58 | [log] [tgz] |
|---|---|---|
| author | Googler <pcloudy@google.com> | Thu Sep 19 07:39:22 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Sep 19 07:42:02 2024 -0700 |
| tree | be71d08511f70fba94e2b10a47882f2741d8930b | |
| parent | 0313b4a2efb9891b23493f74e0d37fced3f0824a [diff] |
Automated rollback of commit 7c761bd6046defb34ada39c66eca686571eec4f4. *** Reason for rollback *** Broke Bazel postsubmit: https://github.com/bazelbuild/bazel/pull/23651#issuecomment-2361083993 *** Original change description *** Update Bazel's embedded JDK to 23 In addition to performance improvements, this JDK release contains a fix for https://bugs.openjdk.org/browse/JDK-8330077, which allows `--watchfs` to handle a configurable number of changes to a watched path rather than maxing out at 500. s390x and ppc64le can only be updated to 22, Windows arm64 can switch to Zulu JDK 21. Closes #23651. PiperOrigin-RevId: 676408630 Change-Id: Iffbb319c20127a3df72e4e29db248550ea328b51
{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
