Continuous Delivery Meets OpenShift
summary
A container-based continuous delivery pipeline runs fully on OpenShift using Jenkinsfile-driven buildconfigs and OpenShift templates to package pipeline as code as deployable apps; images are built from source, deployed into temporary test environments, promoted to dev→stage→prod by tagging, and triggers fire from registry tag changes. The pipeline uses pods-per-build so multiple builds run in parallel, speeding cycles, persists Jenkins state on PVCs, and relies on pure Red Hat technologies to ensure reproducible environments and accelerated by parallel runs promotion while allowing a human gate before production.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:10Environments
- 3:04Traditional environments
- 6:08Service dependencies
- 8:54Problem solving
- 9:30Continuous Integration
- 13:05Continuous Delivery
- 15:53OpenShift
- 18:04Jenkins
- 19:26CD Pipeline
- 22:47Build Pipeline Body
- 24:18Build Config
- 28:15Pipeline Job
- 31:10Summary
- 32:27QA Time
- 34:47Buildconfig
- 40:51Stages
related talks
24mExclude Human – Continuous Deployment and OpenShift
32mContinuous Delivery as a Service
56mContinuous Deployment Pipeline in Kubernetes
40mMicroservice Continuous Delivery
40mContinuous delivery @ Axians with gitlab and openshift
42mCI/CD - Let The Robots Do Their Job!
22mOpenShift, or Kubernetes on steroids
14mBuild It Your Way: Modular Pipelines for Bootable Containers
