How to Continuously Deliver Your Platform with Concourse
summary
Shows how Concourse pipelines automatically fetch tiles from Pivotal Network, upload and stage them in Ops Manager, and hit apply-changes to perform patch and install workflows; pipelines include staged inputs, stemcell upgrades, scheduled triggers (lab checks every 30 minutes) and smoke tests. Large users run this across 12 foundations, cut multi-hour manual upgrade windows (elastic runtime upgrades took 12–24 hours), eliminate Monday-night toil, and report fewer incidents and reliable, repeatable patch automation.
AI-written summary · about
chapters (8)
- 0:00Introduction to platform ops
- 0:56Pivotal culture and CI/CD
- 3:38Concourse architecture
- 8:11Automating platform updates
- 12:39Verizon case study
- 18:41Pipeline demonstration
- 25:57Future roadmap and vision
- 34:55Q&A session
related talks
44mContinuous Delivery with Concourse CI
35mKeeping your Cutting Edge Platform Cutting Edge: Continuous Delivery of Cloud Foundry
46mConcourse: CI/CD, 2020 edition
27mContinuous Delivery of Cloud Native Microservices on the PCF Platform
27mContinuous Delivery of Cloud Native Microservices on the PCF Platform
01h 00mDeep Dive: Self-driving Pipelines: Building the Unbreakable Continuous...
37mGetting Started with Concourse CI
16mConveyor: One-Tool-Fits-All Continuous Software Deployment