Distributed CI with Radicle and Ambient
summary
Explains a distributed CI stack built on Radicle CI with an adapter model (JSON stdin/out over a Unix domain socket to a CI broker), a local-first engine Ambient that runs each job in a fresh, networkless VM to protect host secrets, and uses QEMU for isolation; supports native, container and third‑party adapters (including GitHub Actions); network runs show a few hundred active nodes and just under 10,000 CI runs recorded; a hosted option called Radical Garden targets €5/month for always‑on nodes.
AI-written summary · about
chapters (8)
- 0:00Distributed CI with Radicle
- 4:53GitHub vulnerabilities
- 7:24What Radicle is
- 11:40Radicle CI design
- 19:36Ambient CI engine
- 25:24Radicle adoption challenges
- 29:01Why decentralization matters
- 30:52Q&A
related talks
13mProviding Continuous Integration at CERN
26mDeep Dive: CNCF CI
27mRe-thinking CI bottlenecks with Distributed Execution
43mRewriting an Old CI/CD on GitHub Actions for 280 Contributors?
26mFaster, Cheaper, Leaner: Horizontally Scaling a CI Pipeline
24mIntro: CNCF CI
34mMigrating GitHub Actions with Nested Virtualization to a Cloud Native Ecosystem
31mFrom Jenkins-under-your-desk to resilient service