Automated PCF Upgrades with Concourse - Rich Ruedin, Express Scripts
summary
Automates PCF patching using Concourse pipelines that watch for tile and stemcell artifacts, download to an internal S3, and promote a product through nine foundations; pipelines run every 30 minutes, use a fork of the PCF-pipelines repo and the fly CLI, and include automated smoke tests that deploy Java/Ruby/Node apps, bind services, and exercise MySQL, Redis and SCS. Result: single-patch promotion drops from ~45 to ~5 business days, catching buildpack and MySQL regressions before production.
AI-written summary · about
chapters (15)
- 0:00Introduction and agenda
- 0:23Challenge and initial goal
- 1:27Why automation is necessary
- 2:30Concourse setup and requirements
- 3:33PCF Pipelines overview
- 4:59Environment configuration
- 5:42Post-upgrade considerations
- 7:28Integrations and notifications
- 8:32Multi-foundation support
- 9:56Validation pipeline structure
- 14:13Testing custom services
- 16:00Measuring success metrics
- 18:51Benefits of automated upgrades
- 19:14References and resources
- 20:28Q&A session
related talks
35mKeeping your Cutting Edge Platform Cutting Edge: Continuous Delivery of Cloud Foundry
27mContinuous Delivery of Cloud Native Microservices on the PCF Platform
28mProject 42 - Making CI/CD a First Class Citizen in...
27mContinuous Delivery of Cloud Native Microservices on the PCF Platform
44mContinuous Delivery with Concourse CI
01h 00mDeep Dive: Self-driving Pipelines: Building the Unbreakable Continuous...
46mConcourse: CI/CD, 2020 edition
29mCI That Scales With your Project