Container pipeline for devs and enterprises alike!
summary
CentOS Container Pipeline is rearchitected as an OpenShift-native Jenkins pipeline that runs each build in a dynamic pod, replaces Beanstalkd, and cuts deploy cycles from ~30 minutes to about 5. It lints Dockerfiles with Project Atomic tools, builds images, scans for RPM/pip/npm/gem updates plus RPM verification and runtime capability checks, and does weekly scans and notifications. Automatic rebuilds fire on git push and parent-image changes — the system auto-rebuilt about 500 images during Meltdown/Spectre — and it proves viable with buildah for 250 images, though OpenShift alerting and Jenkins sync and privileged builds remain friction points.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:58Core Features of the Pipeline
- 4:27Child Relationship
- 6:16Summary of the Features
- 7:03Workflow of the Container Pipeline Service
- 13:24Development and Deployment Cycles
- 13:43Stability
- 18:24Privilege Mode
related talks
06mBuilding Continuous Delivery Pipelines
13mEvolution of containers in continuous integration
52mAdding containers to your CI/CD pipeline
52mContinuous Delivery with Containers: The Good, the Bad, and the Ugly
14mBuild It Your Way: Modular Pipelines for Bootable Containers
35mBuilding Reusable DevSecOps Pipelines on a Secure Kubernetes Platform
43mMoving the Unmovable: migrating from VMs to K8s
23mOrchestration and CI/CD