CI for OpenShift: Prow, ci-operator and the future
summary
OpenShift CI migrates from Jenkins → Prow and uses Prow components like hook and tide merges in batches to enforce merge criteria, plus ci-operator to declaratively build component images, run unit/integration/e2e tests and assemble release payloads. Jobs are presubmits, postsubmits and periodics; prowgen generates job YAML to remove boilerplate. Current fleet runs about 700 jobs for 120 repos, the config is ~35k lines of YAML, and roughly 2,600 jobs executed in 24 hours with ~600 full-cluster deploy tests taking ~40 minutes each. Rehearsal and failure investigation are next priorities.
AI-written summary · about
chapters (12)
- 0:00Start
- 3:32SELF-SERVICE AND OWNERSHIP
- 4:22HISTORY
- 5:45KUBERNETES-BASED CI/CD SYSTEM
- 8:40DEVELOPMENT WORKFLOWS
- 10:47MERGING
- 14:36EXECUTE POD
- 34:10STATUS RECONCILER
- 36:27JOB REHEARSALS
- 38:41INVESTIGATION TOOLS
- 39:33METRICS & ALERTS
- 42:31redhat
related talks
42mCI/CD - Let The Robots Do Their Job!
22mCI that CIs itself: Rehearsals in OpenShift CI
46mKubernetes native CI/CD with Prow
36mSIG Testing Deep Dive
20mBuilding, Managing and Automating Clusters at Scale With Prow
36mIntro: SIG Testing
35mOpenShift CI: What if we stopped retesting everything all the time?
38mRunning Multi-Arch Builds & Tests in OpenShift CI/CD