The “C” in CI/CD is not for “Closed”
summary
Argues that closed-source CI/CD (GitHub Actions, Buildkite, CircleCI) now runs much of open source and that this creates vendor lock‑in; proposes building a pipeline compiler that analyzes a repo and emits pipelines for multiple backends (Buildkite, GitHub Actions, Jenkins) so the same workflow runs locally and in CI. Notes existing tools (Dagger, pre-commit, Bazel/Pants) but rejects reinventing whole build systems; prototype is incubating at Ivan, funded as research time, with a 1–2 year plan to open source it.
AI-written summary · about
chapters (7)
- 0:00Introduction to talk
- 1:47Current CI/CD landscape
- 7:23Funding models for open source
- 13:23Problems with existing CI/CD
- 18:18Building better open source tools
- 24:14Design pitfalls to avoid
- 27:52Q&A
related talks
40mSecure by Default: Building an AI-Augmented, OSS-Powered Reusable CI/CD Pipeline
27mRun Your CI in Code, Not YAML
23mBuilding a Secure By-Design Pipeline with an Open-Source Stack
30mCI/CD Panel (Teams & Tools)
22mCI and CD as a Service: A multi-vendor driven system
24mCI/CD Best Practices to Deliver Software Faster
48mInfrastructure-Agnostic Continuous Delivery
29mOpen-Source Framework for AI-Powered CI/CD Pipelines