Your CI Pipeline is the Platform
summary
Claim: the CI pipeline is the platform because the repo holds the app, the pipeline and the deployment artifacts so delivery is reproducible. Uses Jenkins running in Kubernetes to spawn ephemeral build pods, runs a three-stage pipeline (compile/test, helm lint + dry-run, publish image), builds on PRs and on merge runs helm install/upgrade for rolling deploys. Also demoed draft creating Dockerfile and helm chart scaffolds. The demos succeed end-to-end: image pushed, chart rendered, app updated in cluster.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:05Deis tools and Kubernetes
- 3:55Platform power and limits
- 6:26CI pipeline design goals
- 8:12Demo: Croc Hunter app
- 12:30Azure Container Service
- 14:16Helm charts and packages
- 17:26Demo results and summary
- 18:10Introducing Draft
- 19:02Draft demo with Go app
- 22:37Q&A
related talks
25mIncrease App Confidence Using CI/CD and Infrastructure as Code
52mAdding containers to your CI/CD pipeline
45mBecoming a Plumber: Building Deployment Pipelines
40mMicroservice Continuous Delivery
38mCI is Essential but not Sufficient for an Effective Application Delivery Workflow
52mFrom 0 to Continuous Deployments with Kubernetes, Helm and GitLab
22mLet's Build A CI CD Pipeline
27mRun Your CI in Code, Not YAML