BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-cz-2026//talk//B7J3LX
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-devconf-cz-2026-B7J3LX@pretalx.devconf.info
DTSTART;TZID=CET:20260618T101500
DTEND;TZID=CET:20260618T105000
DESCRIPTION:Most OpenShift developers saw the dreaded Tide retest many time
 s. All jobs are green and for SOME REASON Tide decides to run everything a
 gain and now the PR will not merge for several hours. It is not a bug\, it
  is a feature. What if the green jobs actually ran a month ago when the co
 de was much different? They surely do not provide reliable signal for a me
 rge decision. They need to be retested.\n\nIt is indeed a feature\, but th
 at feature comes at a cost. Retests take time. They cost money. What if we
  stopped doing them? What would we save\, and what risk would we open ours
 elves to? I will explore that in this talk.\n\nThe talk aims to be of inte
 rest even to attendees not familiar with OpenShift CI and Tide. These atte
 ndees may find it useful as a case study of how OpenShift organization mer
 ges code at scale\, how it sets up quality gates\, and what factors and tr
 adeoffs affect the developer experience in such a system.
DTSTAMP:20260430T125242Z
LOCATION:D0206 (capacity 154)
SUMMARY:OpenShift CI: What if we stopped retesting everything all the time?
  - Petr Muller
URL:https://pretalx.devconf.info/devconf-cz-2026/talk/B7J3LX/
END:VEVENT
END:VCALENDAR