commit | eda9160d84500fbcb2afa1e85a8e49ee95571d1a | [log] [tgz] |
---|---|---|
author | Jakub Bujny <jakubbujny@gmail.com> | Wed Oct 02 04:00:58 2019 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 02 04:01:49 2019 -0700 |
tree | 748910e87388678534e5ef2e45981478dde6d2fc | |
parent | c41830d82f65f6d6f09c40acceb5b8c32e2b6d60 [diff] |
Describe known issue when in-mem state is lost when running bazel builds inside docker containers e.g. in CI I hit that problem and discovered answer by reading that doc: https://docs.bazel.build/versions/master/user-manual.html#flag--batch I was trying to understand why my jobs on CI takes around 20s even with caching but in dockers when locally it was like 200 ms. So maybe it would be better to place it in docs for future generations. Closes #6657. PiperOrigin-RevId: 272406338
{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:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.