diff options
| author |  Shreya Bhattarai <shreyax@google.com> | 2016-12-19 22:51:25 +0000 |
|---|---|---|
| committer |  Yue Gan <yueg@google.com> | 2016-12-20 06:12:30 +0000 |
| commit | c5724bc083e26ba81bc275125f54900d50c2c659 (patch) | |
| tree | e681c12a53ef9134bcc00c0b78d6e3379a1e8db5 /site/versions | |
| parent | 5c8d4274356a27a2a7a2998cdd7b0d9095c2e0b6 (diff) | |
Clarify potentially confusing documentation relating to blaze server processes.
--
PiperOrigin-RevId: 142489262
MOS_MIGRATED_REVID=142489262
Diffstat (limited to 'site/versions')
| -rw-r--r-- | site/versions/master/docs/bazel-user-manual.html | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/site/versions/master/docs/bazel-user-manual.html b/site/versions/master/docs/bazel-user-manual.html index 8cba504fd8..d29ad06c1c 100644 --- a/site/versions/master/docs/bazel-user-manual.html +++ b/site/versions/master/docs/bazel-user-manual.html @@ -72,12 +72,14 @@ title: User Manual </p> <p> When you run <code>bazel</code>, you're running the client. The - client finds the server based on the path of the base workspace directory - and your userid, so if you build in multiple workspaces, you'll have - multiple Bazel server processes. Multiple users on the same - workstation can build concurrently in the same workspace. If the - client cannot find a running server instance, it starts a new one. - The server process will stop after a period of inactivity (3 hours, + client finds the server based on the output base, which by default is + determined by the path of the base workspace directory and your + userid, so if you build in multiple workspaces, you'll have multiple + output bases and thus multiple Bazel server processes. Multiple + users on the same workstation can build concurrently in the same + workspace because their output bases will differ (different userids). + If the client cannot find a running server instance, it starts a new + one. The server process will stop after a period of inactivity (3 hours, by default). </p> <p> |