| commit | b0119fa76475e69963be8d60d43cc2cd5680492b | [log] [tgz] |
|---|---|---|
| author | pcloudy <pcloudy@google.com> | Tue Sep 09 02:05:43 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Sep 09 02:07:11 2025 -0700 |
| tree | e87bb4c262cafa510fd41698cc0a8c959e7e961c | |
| parent | 8004d7c52171deed3cd5c5a0c8457213d8f956ce [diff] |
Automated rollback of commit 1e50d2bb74dbe304777564353640972d2cf6bc52. *** Reason for rollback *** This change is breaking some users Context: https://bazelbuild.slack.com/archives/CA31HN1T3/p1757278114180499 *** Original change description *** Use the system trust store by default with the embedded JDK Users can't easily update the certificates in the embedded JDK and arguably shouldn't even have to be aware of the fact that Bazel relies on a bundled JVM. Since JDK 23 made it possible to rely on the system store on all major OSes, do so by default. RELNOTES[INC]: Bazel releases that include a bundled JDK now use the system trust store for certificates by default. Set `-Djavax.... *** PiperOrigin-RevId: 804800915 Change-Id: I3cb40a52efd5c1d392bb4fabecd2159c6781b206
{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
