25 Years of (mistakes) Learning in CI/CD
summary
25 years of CI/CD evolution from ClearCase and monthly third Wednesday builds that take a week to merge, to Java’s “compile once” portability, to Jenkins + heavy plugins causing cross-team coupling, to CircleCI’s pipeline-as-code and Docker/Kubernetes for environment parity. Specific takeaways: one person used to own the build as a build master, log4j ships ~20 versions in five years, artifact managers (Artifactory/Nexus), caching and parallel pipelines cut feedback time, and keep CI config in repo to allow safe, versioned build changes.
AI-written summary · about
chapters (5)
related talks
15mCI/CD: A History Lesson
24mCI/CD Best Practices to Deliver Software Faster
48mDemystifying CI/CD
48mStrong Foundations: Insightful learning vs trial-and-error in CI/CD
13mEvolution of containers in continuous integration
34mContinuous Integration: A Bittersweet Love Story
01h 10mCreating efficient, convenient and reliable CI
32mPractical Tips & Tricks for CI/CD Success
