CI that CIs itself: Rehearsals in OpenShift CI
summary
OpenShift CI runs the changed job definitions from the open-shift-release repo as dry runs: it creates ProwJob CRs so the cluster actually executes them, inlines or temp-creates configmaps and converts periodics to pre-submits to make results reportable. PJ Rehearse (the pre-submit tool) compares PR vs baseline, patches names/targets, injects configs and submits jobs for ~2000 jobs across 200 repos. It works but has pain points: no single-job rerun and a 35-job limit to avoid massive rehearsals. Prow CI builds other Prow jobs. PJ Rehearse inlines config and creates ProwJob CRs.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 4:40Rehearsals
- 5:37How it works
- 10:21More about it
- 11:50Proud jobs
- 12:34The magic
- 15:18The second magic
- 17:23The advantage
- 18:51Cons
related talks
49mCI for OpenShift: Prow, ci-operator and the future
35mOpenShift CI: What if we stopped retesting everything all the time?
36mSIG Testing Deep Dive
36mIntro: SIG Testing
20mBuilding, Managing and Automating Clusters at Scale With Prow
36mThinking like a site reliability engineer to improve CI
47mContinuous Delivery Meets OpenShift
25mCI/CD on OpenShift for developers