Petr Muller
where else to find them
no profile links on file
what they talk about
where they keep going back
- DevConf.CZ4 editions2019–2026
on a stage with
never shared a talk
who talks about the same things
- Jessie Zhu3 talks
- Sen Lu3 talks
- Steve Kuznetsov2 talks
- Arsh Sharma13 talks
- Cole Wagner3 talks
- Urvashi Mohnani18 talks
| title | conference | date |
|---|---|---|
| OpenShift CI: What if we stopped retesting everything all the time? | DevConf.CZ 2026 | 2026-06-18 |
OpenShift CI uses prow jobs and Tide retest to speculatively re-run PRs when base changes, but 2/3 of PRs merge without any retest and only 0.8% see additional… | ||
| It's 2030. What Does Prow Look Like? | Maintainer Summit Europe 2026 | 2026-03-22 |
Prow runs owners-file enforcement and automated reviewer assignment across 90+ Kubernetes repos, interprets who can give LGTM or approve, triggers and executes… | ||
| Safe Upgrades: From Tombstones to Recommendations | DevConf.CZ 2023 | 2023-06-16 |
OpenShift adds Conditional Updates by annotating the Cincinnati update graph with metadata and a PromQL self-check so each cluster evaluates if a release… | ||
| CI that CIs itself: Rehearsals in OpenShift CI | DevConf.CZ 2020 | 2020-01-24 |
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… | ||
| CI for OpenShift: Prow, ci-operator and the future | DevConf.CZ 2019 | 2019-01-25 |
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… | ||
| nothing matches | ||