aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/docs/user-manual.html
diff options
context:
space:
mode:
Diffstat (limited to 'site/docs/user-manual.html')
-rw-r--r--site/docs/user-manual.html10
1 files changed, 10 insertions, 0 deletions
diff --git a/site/docs/user-manual.html b/site/docs/user-manual.html
index e817628c9e..f59e18a9aa 100644
--- a/site/docs/user-manual.html
+++ b/site/docs/user-manual.html
@@ -3383,6 +3383,16 @@ adb -s deadbeef install ...
<li><code class='flag'>--skylark_memory</code> dumps a
<href a=https://github.com/google/pprof>pprof</href> compatible .gz file to the specified path.
You must enable memory tracking for this to work.</li>
+ <li><code class='flag'>--action_graph=/path/to/file</code> dumps the state of
+ the internal Bazel action graph in proto format to
+ <code>/path/to/file</code>. You have to run (at least) the analysis phase
+ for the targets you are interested in (for example, <code>bazel build --nobuild
+ //foo:bar</code>). Note that this feature is still experimental, subject to
+ change and will probably be integrated into <code>cquery</code> in the
+ future.
+ <li><code class='flag'>--action_graph:targets=target1,target2,...</code>
+ filters the actions to the comma-separated list of targets when dumping the
+ action graph.</li>
</ul>
<h4 id='memory-tracking'>Memory tracking</h4>