After 12 months of running production CI/CD workloads on Tekton 0.60 following a full deprecation of Jenkins 2.460 across 47 engineering teams, we’ve eliminated 92% of unplanned pipeline downtime, reduced mean time to recovery (MTTR) for failed builds from 47 minutes to 8 minutes, and cut annual CI/CD infrastructure costs by $210,000. This is the unvarnished, benchmark-backed story of why we left Jenkins, how we migrated without breaking production, and what we’d do differently if we started today.

📡 Hacker News Top Stories Right Now

Ghostty is leaving GitHub (2039 points)

Bugs Rust won't catch (66 points)

Before GitHub (345 points)

How ChatGPT serves ads (220 points)

Show HN: Auto-Architecture: Karpathy's Loop, pointed at a CPU (47 points)

Key Insights

Tekton 0.60 pipelines achieved 99.98% uptime over 12 months, vs 97.2% for Jenkins 2.460 over the prior 12 months

Jenkins 2.460’s plugin sprawl (142 plugins across teams) caused 68% of all pipeline failures; Tekton’s native Kubernetes integration…