Our Butler in the X Factory Show, Lesson Learned Trying to Modernize CI/CD for Cloud...
summary
Claim: replacing Jenkins wholesale is risky because Jenkins plus Jenkins Kubernetes plugin and Helm + Configuration as Code lets teams run dynamic, pod-based agents but still forces heavy maintenance. Tried Jenkins X (JX) as an opinionated CI/CD platform, built a prototype and later rolled back when contributions dried up and Jenkins X (JX) abandoned by CloudBees left the project idle. Recommendation is pragmatic: prefer mix CI with Argo CD for deployments, pick graduated CNCF projects (Argo, Tekton, Flux) and weigh vendor-backed commercial options.
AI-written summary · about
chapters (9)
- 0:00CI/CD modernization motivation
- 3:55Jenkins and Kubernetes plugins
- 10:16Jenkins cloud-native limits
- 13:26Jenkins X adoption challenges
- 16:58Stability in CI/CD selection
- 20:11CNCF project maturity
- 21:58Mixing CI/CD tools
- 24:04Commercial vs open source CI/CD
- 25:08Final recommendations
related talks
23mMoving from Jenkins to Jenkins X: Scaling and Accelerating CI/CD
01h 00mJenkins X @ 2.0, A CI/CD Solution for DevOps on k8s
06mJenkins X: Lessons Learned
47mSave Private Jenkins!
39mAccelerate your CI/CD on Kubernetes with Jenkins X
49mCloud Native CI/Cd with Jenkins X and
42mJenkins X, Continuous Delivery for Kubernetes
47mGitOps, Jenkins X & the Future of CI/CD