Tan Wang
Tan Wang
I'd like to have different logical remote execution services, to separate local vs. CI. It seems like this should be achievable through `--remote_instance_name=local` and `--remote_instance_name=ci` However, if I do: *...
``` bazelisk run //src/main/java/build/buildfarm:buildfarm-server -- --jvm_flag=-Djava.util.logging.config.file=$PWD/examples/server-logging.properties $PWD/examples/config.minimal.yml ``` ``` bazel run //src/main/java/build/buildfarm:buildfarm-shard-worker -- --jvm_flag=-Djava.util.logging.config.file=$PWD/examples/worker-logging.properties $PWD/examples/config.minimal.yml ``` then building something remotely, this is what comes out of the worker console logs:...
Question: **Is there any workaround to keep the `bazel-java-sdk` code compatible with remote execution?** I recently moved to a remote execution setup. I noticed now that the build event JSON...