DevOps in the Era of Containers. Come Learn What Has Changed.
summary
Claims that CI/CD steps run as disposable Docker images instead of installing tools on VMs and demonstrates it on Codefresh using node 11 image, Python 3.7, Go 1.7.1 and an AWS CLI image. Shows caching via a per-pipeline volume so node_modules persist across steps and builds, removes the need for version managers or operator tickets, builds Docker images on the fly (installing mocha jasmine protractor) and runs pipelines end-to-end — an example finishes in about 32 seconds.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:41The Basic Software Lifecycle
- 2:06Before Docker - The Dark Ages
- 2:40Docker-based Deployments - Better
- 4:50Resources for Docker as Deployment artifa
- 5:13Build farm before Docker
- 6:45Build farm after Docker
- 7:21Using Docker in Continuous Integration
- 8:05Docker images are everywhere
- 8:50Container per build step
- 12:24Traditional VM based problems
- 16:44Codefresh Pipelines are Future Proof
- 17:27Updating a Tool in a Traditional VM Pipelin
- 20:20Wasting Effort on "Version Managers"
- 22:29Replacing version man with Docker
- 24:40Data Sharing • Steps need to communicate
- 26:48Demo 4 - Node Modules Docker Buld Context
- 29:13Creating Docker Images On-demand
- 32:28Plugins in Traditional CI/CD Platforms
- 33:21Plugin Directory
related talks
27mOptimizing CI/CD Pipelines for Faster Time to Market
19mDevOps Challenges: The Key Is Technical Excellence
56mDevOps in a containerized world
41mDevOps for Adults: Live Cooking Show
26mFuture-Proof Your Platform’s CI/CD Without Developers Noticing a Thing
01mDevOps.js Conference — February 15-16
49mContinuous Delivery at Docker age
01h 00mVintage CI/CD. How and Where to Start