Do We Need Yet Another CD Tool?
summary
Argues that niche gaps, not novelty, drive new CD projects and that many startups duplicate features rather than solve new problems. Reports personal production experience: Jenkins works in production and remains a reliable choice. Compares two modern paths: Tekton for Kubernetes-native pipelines with declarative CRDs, and Argo for workflow-oriented CD with a helpful UI and rollout features. Concludes tool sprawl is real and worth questioning when the unmet need is not specific or surprising.
AI-written summary · about
related talks
37mCollaborative Development: The Only CD That Matters
50mImplementing Cloud Native CI/CD
45mBuilding Your Continuous Delivery Toolkit
48mStrong Foundations: Insightful learning vs trial-and-error in CI/CD
26mOur Butler in the X Factory Show, Lesson Learned Trying to Modernize CI/CD for Cloud...
42mBuilding Your Continuous Delivery Toolkit
27mArchitect CI/CD on Enterprise level
27mThe curious case of the DevOps engineer and other things ...