Used checked in configs with rbe_autoconf when possible (#276)


For users of the rbe ubuntu 16_04 containers, attempt to first find if a published config will work for their chosen Bazel version. If such a config exists, rule only creates BUILD files with aliases pointing to the published configs.

Pulling container / generating configs will only happen if the above step does not find a published config.

Behavior can be overriden with use_checked_in_confs = False,
6 files changed
tree: 1cabec919ab485673c165fbf68d178196adbaa3f
  1. .bazelci/
  2. bazelrc/
  3. configs/
  4. constraints/
  5. container/
  6. examples/
  7. release/
  8. repositories/
  9. rules/
  10. tests/
  11. third_party/
  12. .gitignore
  13. .travis.yml
  14. AUTHORS
  15. CONTRIBUTING.md
  16. CONTRIBUTORS
  17. LICENSE
  18. README.md
  19. WORKSPACE
README.md
Travis CIBazel CI
Build StatusBuild status

bazel-toolchains

https://github.com/bazelbuild/bazel-toolchains is a repository where Google hosts Bazel toolchain configs. These configs are required to configure Bazel to issue commands that will execute inside a Docker container via a remote execution environment.

These toolchain configs include:

  • C/C++ CROSSTOOL file,
  • BUILD file with toolchain rules, and
  • wrapper scripts.

Release information of toolchain configs can be found at: https://releases.bazel.build/bazel-toolchains.html.

This repository also hosts the skylark rule used to generate toolchain configs.