Using containers for Continuous Integration Delivery
summary
Describes running Jenkins on Kubernetes with dynamic Jenkins agents that spawn pods on demand, reusing public images to run Maven and Go side by side, and running Selenium Chrome and Firefox inside the same pod as a selenium hub in a pod for parallel tests. Demonstrates JVM memory failures when a container is limited to 220MB and shows fixes: set per-process -Xmx or rely on JDK 8u131 support for container-aware sizing. Shows GKE/minikube demos, persistent volumes, and warns about docker socket mounts.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:57Docker
- 2:41Microservices
- 3:09Jenkins
- 3:23Add more Jenkins agents
- 4:31Add more masters
- 5:43Docker and Jenkins
- 6:39DrStorm
- 7:21Other plugins
- 8:07Docker Image
- 8:21The Pearling
- 8:49DevOps
- 9:27Kubernetes
- 10:43Pots
- 12:32Persistent storage
- 14:26Kubernetes security context
- 14:49Jenkins networking
- 15:46localhost
- 16:07cluster
- 17:06memory
- 25:04usergroup memory
- 26:26CPU limits
- 27:52Demos
- 38:16Multiple containers
- 39:44Deploy to Kubernetes
related talks
52mContinuous Delivery with Containers: The Good, the Bad, and the Ugly
42mJenkins X, Continuous Delivery for Kubernetes
41mScaling Jenkins
13mEvolution of containers in continuous integration
35mJenkins Scaling and Organization for an Efficient CI
30mContinuous Integration; Tips & Tricks
28mSupercharged Continuous Integration with Docker Containers
01h 06mon