| commit | b02c06748c93a126db95261a77a57903e9dc002d | [log] [tgz] |
|---|---|---|
| author | bazel.build machine account <ci.bazel@gmail.com> | Thu Oct 17 10:37:46 2024 +0200 |
| committer | GitHub <noreply@github.com> | Thu Oct 17 08:37:46 2024 +0000 |
| tree | 066b49b2a6b1f396c8b83fb41208c51d9b913085 | |
| parent | b7a22e7a42f5ae4073c5d2bd49990690d84c30b6 [diff] |
[7.4.0] Properly cancel repository downloads (#24001) When cancelling an asynchronous repository download task, an interrupt signal is sent to the download thread. This doesn't mean that the download stops immediately. Avoid restarting a download until the previous download has actually stopped, so that the new download is able to clean old data without crashing (on Windows). Fixes #21773 Closes #23837. PiperOrigin-RevId: 686175953 Change-Id: I8d75f905b739d38b6cb430d5b5e84fda9a2d14e3 Commit https://github.com/bazelbuild/bazel/commit/48338d2ff33586a0d053e358da6b94e23fe0e2eb Co-authored-by: Fredrik Medley <fredrik@meroton.com>
{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
