Lightning Talk – Bazel Parallel and Asynchronous Artifact Publishing Pipeline
summary
An asynchronous publisher service replaces a single post-build step and pulls the Bazel result store to detect ready outputs, downloads artifacts and uses an image_info macro from rules_docker plus a docker client to pushes only missing layers, then notifies a lightweight promotion service that tags versions. Consumers are sharded by artifact ID so each flow runs on a single-threaded event loop, cutting a previously ~30% publisher bottleneck and running faster than the build.
AI-written summary · about
chapters (8)
- 0:00Artifact publishing pipeline
- 1:26Parallel builds and ordering
- 3:35Promotion service architecture
- 4:41Slow publishing problems
- 5:46Async pipeline redesign
- 7:13Benefits of async approach
- 8:17Future features and deployment
- 9:21Summary
