diff options
| author |  Googler <noreply@google.com> | 2017-08-22 02:53:02 +0200 |
|---|---|---|
| committer |  Damien Martin-Guillerez <dmarting@google.com> | 2017-08-22 09:15:29 +0200 |
| commit | 01f659d7cf2bad3d55b139354759d4f3098f55e4 (patch) | |
| tree | 52ed5cddb373966468812aa6cedf27d1bcca1a30 /site | |
| parent | 49b5bbc665b0cef3bcc9686cb2148e5a2d4ee7c6 (diff) | |
Add a --build_runfile_manifests flag which controls production of
foo_test.runfiles_manifest files. These are the largest local outputs
in many builds, and unnecessary for remote test execution.
RELNOTES: New --build_runfile_manifests flag controls production of runfiles manifests.
PiperOrigin-RevId: 166001477
Diffstat (limited to 'site')
| -rw-r--r-- | site/docs/bazel-user-manual.html | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/site/docs/bazel-user-manual.html b/site/docs/bazel-user-manual.html index 798e592f04..2c797d88de 100644 --- a/site/docs/bazel-user-manual.html +++ b/site/docs/bazel-user-manual.html @@ -1918,6 +1918,15 @@ cores directly from system configuration and will assume 1.0 I/O resource. each individual test (or application) requires its own runfiles tree. </p> +<h4 id='flag--build_runfile_manifests'><code class='flag'>--[no]build_runfile_manifests</code></h4> +<p> + This option, which is enabled by default, specifies whether runfiles manifests + should be written to the output tree. + Disabling it implies <code class='flag'>--nobuild_runfile_links</code>. + + It can be disabled when executing tests on Forge, as runfiles trees will + be created remotely from in-memory manifests. + <h4 id='flag--discard_analysis_cache'> <code class='flag'>--[no]discard_analysis_cache</code></h4> <p> |