| commit | d480c5f5a4f38a4053ed3e3bcc4eaef343923d2d | [log] [tgz] |
|---|---|---|
| author | buchgr <buchgr@google.com> | Wed Apr 03 00:53:34 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 03 00:55:11 2019 -0700 |
| tree | 3aa4f8b3343ccef8f0010e63a3a966e55175d8d4 | |
| parent | 18d702470f14cba937fa914032e3afe6a40d7d96 [diff] |
remote: introduce --experimental_remote_download_outputs=minimal This implements the first milestone of #6862. When specifying --experimental_remote_download_outputs=minimal Bazel will avoid downloading most action outputs when used with remote caching and remote execution. That is, it will only download an action's stdout/stderr as well as .d and .jdeps output files when building C++ and Java. All other output files will only be downloaded on demand, that is if a local action declares a remote output as an input. Enabling this mode currently requires specifying three additional flags to the set of the remote caching/execution flags: $ bazel build ... \ --experimental_inmemory_jdeps_files \ --experimental_inmemory_dotd_files \ --experimental_remote_download_outputs=minimal This mode does not yet interact well with the Build Event Service (--bes_backend=...). Specifically, local file uploads and remote file name conversions are disabled when --experimental_remote_download_outputs=minimal is specified. Lastly, this mode also does not at all interact with Bazel's on disk action cache. That is, all (local) cached state will be lost after restarting the Bazel server. Also changing the value of --experimental_remote_download_outputs between builds will invalidate all (cached) actions. Closes #7905. PiperOrigin-RevId: 241681028
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds 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.