commit | 57c18017de2c6f3ec655d931e3a3ed8060cf84c8 | [log] [tgz] |
---|---|---|
author | Googler <wyv@google.com> | Fri Jan 26 10:55:56 2024 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Jan 26 10:57:35 2024 -0800 |
tree | cc44b93fe593442568ae07bfcba5acfa03bd95a3 | |
parent | 999a26a1d2d652c5f2dbc9a49408869bfda0e2c0 [diff] |
Enable worker thread for repo fetching by default We use virtual threads if available (JDK 21+); if not, we fall back to not using worker threads at all. This approach is slightly safer than straight up setting the default to `virtual` as that would break certain obscure platforms without an available JDK 21. The plan is to cherry-pick this into 7.1.0. Also removed test_reexecute in bazel_workspaces_test since, well, that's the whole point! Fixes https://github.com/bazelbuild/bazel/issues/10515 RELNOTES: The flag `--experimental_worker_for_repo_fetching` now defaults to `auto`, which uses virtual threads from JDK 21 if it's available. This eliminates restarts during repo fetching. PiperOrigin-RevId: 601810629 Change-Id: I9d2ec59688586356d90604fdd328cc985e75d1d4
{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