Continuous Delivery at Docker age
summary
Argues that Docker becomes the immutable application artifact containing app plus its middleware, with Jenkins and GitHub building images, tagging them image tag = git SHA, pushing to a Docker registry and deploying to a cluster (demo uses Docker Toolbox, Docker Compose, Swarm, Docker Machine and IBM Bluemix). Shows a working pipeline where Jenkins builds Docker image and a one-click promotion moves the exact same image from dev to UAT to production; data is externalized and ops/platforms host containers, not application internals.
AI-written summary · about
chapters (11)
- 0:00Introduction to talk
- 1:26Continuous delivery challenges
- 2:52Docker as central artifact
- 6:50Immutable containers and data
- 10:45Team collaboration with Docker
- 16:27Local development with Docker
- 20:40Automated deployment pipeline
- 27:52Microservices and topology
- 31:35Docker’s multi-faceted role
- 36:50Cost savings and cloud transition
- 40:23Q&A session
related talks
52mContinuous Delivery with Containers: The Good, the Bad, and the Ugly
40mSpeed up software delivery
52mBringing Continuous Delivery to Cloud-Scale with Jenkins, Docker and
31mBuilding a private CI/CD pipeline with Java and Docker in the Cloud
06mBuilding Continuous Delivery Pipelines
41mContinuous Delivery with Docker Containers and Java EE
34mContinuous Delivery with Jenkins Workflow
43mLightweight PaaS for Jenkins CI Environments with Docker