.bazelrc: Cache-only use of buildbuddy.

Also adds a Bazelisk helper on Windows.

.bazelrc

@@ -25,4 +25,17 @@ build:remote --remote_executor=grpcs://remote.buildbuddy.io
 
 build:remote --jobs=50
 
+# Use buildbuddy for cache only, by passing --config=remotecache.
+# This should be fine for this open source project.
+build:remotecache --bes_results_url=https://app.buildbuddy.io/invocation/
+build:remotecache --bes_backend=grpcs://remote.buildbuddy.io
+build:remotecache --remote_cache=grpcs://remote.buildbuddy.io
+build:remotecache --remote_timeout=3600
+build:remotecache --remote_executor=grpcs://remote.buildbuddy.io
+
+# readonly:
+#build:remotecache --noremote_upload_local_results # Uploads logs & artifacts without writing to cache
+# toplevel:
+#build:remotecache --remote_download_toplevel # Helps remove network bottleneck if caching is enabled
+
 try-import %workspace%/.bazelrc.buildbuddysecrets

.gitignore

@@ -38,4 +38,5 @@ yatc.ico.png
 # Ignore generated output. Although valuable (after all, the primary purpose of `bazel-compile-commands-extractor` is to produce `compile_commands.json`!), it should not be checked in.
 /compile_commands.json
 # Ignore the directory in which `clangd` stores its local index.
-/.cache/
+/.cache/
+bazelisk-windows-amd64.exe

bazel.bat

@@ -0,0 +1,2 @@
+set BAZEL_VC=C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC
+bazelisk-windows-amd64.exe %*