Integrating Software Stacks with BuildStream 2.0 and the Remote...
summary
BuildStream 2.0 implements the Remote Execution API so integration pipelines can push and pull content‑addressed build artifacts from shared caches and run builds on build farms; demo builds a GNU Hello in a sandboxed Alpine rootfs and the local cache skips rebuilds when inputs match. Real projects use it: the FreeDesktop SDK builds ~600 components for four architectures and shares gigabytes via REAPI, and a DCS reference implementation using BuildStream is certified to ISO 26262. Trade‑off: elements rebuild entirely on any source‑commit change.
AI-written summary · about
chapters (12)
- 0:00INTEGRATING SOFTWARE STACKS
- 0:22THE BASIC PROBLEM
- 1:33A BRIEF HISTORY OF INTEGRATION TOOLS
- 4:21THE REMOTE EXECUTION API
- 8:52REAPI CLIENTS
- 14:15THINGS TO BE AWARE OF
- 15:58REAPI INFRASTRUCTURE
- 26:49BUILDSTREAM - EXAMPLE PROJECT
- 27:41CASE STUDY: FREEDESKTOP SDK
- 30:22CASE STUDY 2
- 30:58CASE STUDY: DCS
- 33:55HAPPY INTEGRATING
related talks
42mIntegrating with ease: Leveraging BuildStream interaction with Bazel build
22mBuildGrid
30mThe Bitter and the Sweet of Running a Planet-Scale Build &...
24mFaster Builds With Remote Execution and Caching
55mSo You're Trying to Support a Medium Sized Studio....
46mThe Software Factory
11mIntroducing Remote Bazel
30mA Deep Dive into a Cross-Platform Build Farm