Continuous Delivery with Concourse CI
summary
Concourse CI is presented as a replacement for Jenkins for Cloud Foundry CI/CD, running each build inside Docker-based workers and keeping pipeline definitions alongside source code (pipelines-as-code). The stack components include Postgres, garden, baggageclaim, scalable web and worker instances, and the fly CLI to set pipelines; an example pipeline runs tests on three platforms then creates a GitHub release and uploads the artifact. Operators report that builds become green end-to-end but there are occasional resource/worker bugs and a steep learning curve.
AI-written summary · about
chapters (9)
- 0:00Concourse CI intro
- 4:00Why Concourse CI
- 10:23Concourse architecture
- 17:27First pipeline
- 23:54Pipeline demo
- 33:20Secrets with Vault
- 36:09Concourse pitfalls
- 39:46Concourse vs alternatives
- 42:41Q&A
related talks
29mCI That Scales With your Project
46mConcourse: CI/CD, 2020 edition
29mConcourse in the Real World: A Case Study in CI/CD and DevOps - Greg Meyer & Bryan Kelly, Cerner
01h 09mContinuous Deployment to the Cloud
22mLet's Build A CI CD Pipeline
28mProject 42 - Making CI/CD a First Class Citizen in...
27mContinuous Delivery of Cloud Native Microservices on the PCF Platform
27mContinuous Delivery of Cloud Native Microservices on the PCF Platform