Building Continuous Delivery Pipelines
summary
A pipeline that spins up containerized build slaves on demand replaces brittle pet servers: Jenkins + Docker + Kubernetes coordinate to run tests inside developer-specified images, with job configs kept as .ci.yml checked into repo and a GitHub hook/CI plugin creating jobs automatically. Example parallelization runs tests across 5 Ruby versions by provisioning five containers concurrently; the system runs in AWS/DigitalOcean and demonstrably scales and reduces wasted resources.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:23CI Wishlist 1. No manual server env setup
- 1:383. Version Controlled job configurations
- 2:08Solution No manual server env setup
- 2:38Solution Push button Job Creation
related talks
13mEvolution of containers in continuous integration
30mContinuous Integration; Tips & Tricks
35mJenkins Scaling and Organization for an Efficient CI
52mBringing Continuous Delivery to Cloud-Scale with Jenkins, Docker and
25mContainer pipeline for devs and enterprises alike!
34mContinuous Delivery with Jenkins Workflow
52mAdding containers to your CI/CD pipeline
52mContinuous Delivery with Containers: The Good, the Bad, and the Ugly
