Bazel Federation + Q&A
summary
A GitHub repo maps specific rule-set URLs, versions and checksums into a single GitHub repo of pinned rule sets that exposes Bzl repository/macros so a workspace can pull a federation HTTP archive and request “give me rules_cc” while the federation hides transitive dependencies and toolchain setup. CI (called bazelci tests) runs integration and presubmit checks; current preview is 0.0.1 preview supporting C++, Java, Python and Skylib, with workarounds for Starlark’s inability to load inside macros and plans to onboard Go, Docker and automated release tooling.
AI-written summary · about
chapters (14)
- 0:00Bazel Federation intro
- 1:04Bazel rules challenges
- 3:32Dependency and versioning issues
- 4:36Bazel Federation tech
- 6:00Federation in workspace
- 7:23Simplifying dependencies
- 8:49Limitations and future
- 9:30Managing Bazel versions
- 10:54Ruleset guidelines and CI
- 11:57State and roadmap
- 13:45Best practices and tooling
- 15:31Release automation
- 16:57Enhancing Bazel usability
- 18:02Q&A
