Skip to content

Conversation

@benjaminp
Copy link
Contributor

@benjaminp benjaminp commented Feb 11, 2022

Switch from the deprecated rbe_autoconfig workspace rule to using bazel-toolchain's rbe_configs_gen. I.e., I ran:

$ rbe_configs_gen --toolchain_container=gcr.io/bazel-public/ubuntu2004-java11@sha256:69a78f121230c6d5cbfe2f4af8ce65481aa3f2acaaaf8e899df335f1ac1b35b5 --exec_os=linux --target_os=linux --output_config_path remote_config --output_src_root . -generate_java_configs=false

Really, the only thing this gives us is the cc toolchain configuration for the container image. But that is a substantial amount of crosstool goop.

.bazelrc configuration is generally simpler now. We can also upgrade to Bazel 5.

Fixes #18.

Switch from the deprecated rbe_autoconfig workspace rule to using bazel-toolchain's rbe_configs_gen. I.e., I ran:

$ rbe_configs_gen --toolchain_container=gcr.io/bazel-public/ubuntu2004-java11@sha256:69a78f121230c6d5cbfe2f4af8ce65481aa3f2acaaaf8e899df335f1ac1b35b5 --exec_os=linux --target_os=linux --output_config_path remote_config --output_src_root . -generate_java_configs=false

Really, the only thing this gives us is the cc toolchain configuration for the container image. But that is a substantial amount of crosstool goop.

.bazelrc configuration is generally simpler now. We can also upgrade to Bazel 5.

Fixes #18.
@benjaminp benjaminp merged commit f5ad6e3 into main Feb 11, 2022
@benjaminp benjaminp deleted the new-config branch February 11, 2022 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

replace rbe_autoconfig with rbe_configs_gen

3 participants