Kubernetes First Continuous Delivery for Developers
summary
Jenkins X claims to make CI/CD developer-first on Kubernetes by using a CLI, GitOps-driven environment repos, and standard tools like Maven, Docker, Helm and ChartMuseum. It boots a Spring quickstart, runs a Maven build, pushes a Docker image, generates a Helm chart, and opens a PR to the staging environment repo; merges auto-trigger a master build and can create ephemeral preview environments per pull request. Demos sometimes hiccup but the pipeline, promotion and preview flow is implemented end-to-end.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:30Who am I
- 1:26About this talk
- 3:35What will you do
- 6:42Architecture
- 11:20Jenkins Quick Start
- 11:40Jenkins Create Spring
- 18:13Config Pipeline
- 21:50Starting Pipeline
- 25:48What is JenksEX
- 27:54JenksEX overview
- 31:15What is in it for
- 34:33Demo
- 37:41Kubernetes Environment
- 38:32Testing
- 40:23Creating a pull request
- 41:48Testing the service
- 42:50Chatups
- 45:11Staging
- 48:18How it works
- 49:12Questions
related talks
50mContinuous Deployment With Jenkins X And Kubernetes
39mAccelerate your CI/CD on Kubernetes with Jenkins X
35mJenkins X: Easy CI/CD for Kubernetes
42mJenkins X, Continuous Delivery for Kubernetes
50mEnd to End automation and Continuous Delivery of Microservices (...)
39mJenkins X Progressive Delivery For Kubernetes
23mMoving from Jenkins to Jenkins X: Scaling and Accelerating CI/CD
47mGitOps, Jenkins X & the Future of CI/CD