| commit | 55d18aed1c8deccd76ea9c2f1e9177947e808274 | [log] [tgz] |
|---|---|---|
| author | Richard Smith <richard@metafoo.co.uk> | Tue Jan 23 11:20:41 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 23 11:23:51 2024 -0800 |
| tree | bdb58b9f5739e493b7ccf5b246c1e6c8cb38e45c | |
| parent | d0831f5e3d9b83a1dbae10e61150517fe4966f28 [diff] |
Suggest to use bazelisk as a lockfile best practice. As noted in #20974, the bazel version contributes to the lockfile, so all developers need to be using the same bazel version to avoid lockfile skew stemming from bazel version skew. Closes #20991. PiperOrigin-RevId: 600851571 Change-Id: Ib897e1a7d5fb44357bd066849d2ee160cd4529d4
{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
