diff options
| author |  Tom Payne <twpayne@gmail.com> | 2016-12-16 16:36:06 +0000 |
|---|---|---|
| committer |  John Cater <jcater@google.com> | 2016-12-16 17:07:31 +0000 |
| commit | 77e01d8aeadb5d987c2314ce3f6c48a3778f2247 (patch) | |
| tree | 8c15f8a34b8237dfe05751285d496dc7f0ee4433 /src/main/java | |
| parent | 9012bf1676bd6426229625e2567bfa399f89dabe (diff) | |
Fix formatting of README.md
A number of the shorter commands were not displayed in a code block, making them trickier to copy and paste into a console.
Closes #2257.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2257
PiperOrigin-RevId: 142262893
MOS_MIGRATED_REVID=142262893
Diffstat (limited to 'src/main/java')
| -rw-r--r-- | src/main/java/com/google/devtools/build/lib/remote/README.md | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/src/main/java/com/google/devtools/build/lib/remote/README.md b/src/main/java/com/google/devtools/build/lib/remote/README.md index b0598acb21..b913ff4813 100644 --- a/src/main/java/com/google/devtools/build/lib/remote/README.md +++ b/src/main/java/com/google/devtools/build/lib/remote/README.md @@ -4,14 +4,18 @@ configuration. If you already have a separate Hazelcast cluster you can skip this step. +``` java -cp third_party/hazelcast/hazelcast-3.6.4.jar \ com.hazelcast.core.server.StartServer +``` - Then you run Bazel pointing to the Hazelcast server. +``` bazel --host_jvm_args=-Dbazel.DigestFunction=SHA1 build \ --hazelcast_node=localhost:5701 --spawn_strategy=remote \ src/tools/generate_workspace:all +``` Above command will build generate_workspace with remote spawn strategy that uses Hazelcast as the distributed caching backend. @@ -21,15 +25,19 @@ Hazelcast as the distributed caching backend. - First run the remote worker. This will start a standalone Hazelcast server with default configuration. +``` bazel-bin/src/tools/remote_worker/remote_worker \ --work_path=/tmp/remote --listen_port 8080 +``` - Then run Bazel pointing to the Hazelcast server and remote worker. +``` bazel --host_jvm_args=-Dbazel.DigestFunction=SHA1 build \ --hazelcast_node=localhost:5701 \ --remote_worker=localhost:8080 \ --spawn_strategy=remote src/tools/generate_workspace:all +``` # How to run a remote worker with a remote cache server. @@ -37,22 +45,30 @@ with default configuration. configuration. If you already have a separate Hazelcast cluster you can skip this step. +``` java -cp third_party/hazelcast/hazelcast-3.6.4.jar \ com.hazelcast.core.server.StartServer +``` - Then run the remote cache server: +``` bazel-bin/src/tools/remote_worker/remote_cache --listen_port 8081 +``` - The run the remote worker: +``` bazel-bin/src/tools/remote_worker/remote_worker \ --work_path=/tmp/remote --listen_port 8080 +``` - Then run Bazel pointing to the cache server and remote worker. +``` bazel --host_jvm_args=-Dbazel.DigestFunction=SHA1 build \ --hazelcast_node=localhost:5701 \ --remote_worker=localhost:8080 \ --remote_cache=localhost:8081 \ --spawn_strategy=remote src/tools/generate_workspace:all +``` |