commit | f6344ffcacdea6c4a61e112d0f60beda8068eac5 | [log] [tgz] |
---|---|---|
author | Googler <jhorvitz@google.com> | Fri Jul 21 14:51:05 2023 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Jul 21 14:55:12 2023 -0700 |
tree | 1ad897a56cb71bdf0cdade4506aba18659d8f020 | |
parent | f4b01b14c6be37606f490c5a3758bcc6a40b4b2f [diff] |
Run idle server GC immediately following a `--nokeep_state_after_build_command` instead of waiting 10 seconds. This helps to ensure that weakly reachable objects are not resurrected. Using the idle server task avoids blocking command completion on a full GC, which can take multiple seconds. PiperOrigin-RevId: 550056326 Change-Id: Ia55a2360a196ee0f0dcbb0ac6b6baa11e39e244d
{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