CONTINUOUS DELIVERY: Five Years On
summary
Describes Cloudesire’s continuous delivery pipeline built over five years: issues flow to pull requests to master which trigger containerized builds and tests, then push Docker images to a registry and update the staging environment with weekly or daily deploys. Migration from Jenkins to GitLab CI enabled better isolation and parallelism without raising the ~€350/month infrastructure bill; infrastructure and releases are managed with Terraform and Chef (Cookbooks tested with Test Kitchen) plus a ~200-line release script, with monitoring via Prometheus and Sentry and Slack notifications.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 5:23CD principles
- 13:15Issue workflow
- 16:45Jenkins to CircleCI
- 21:11SonarQube static analysis
- 24:48Docker benefits
- 28:47Terraform infra
- 30:54Release process
- 32:42Post-release monitoring
- 35:32Slack notifications
- 38:22Prometheus and Grafana
- 40:28Graylog logs
- 41:12Future plans
related talks
01h 03mYet Another Continuous Delivery Talk
02h 47mPipes on Pipelines
07mLightning Talk: Continuous Delivery with Kubernetes: The Prequel
30mOur Continuous Delivery Journey
01h 01mContinuous Delivery with GitLab CI and Kubernetes
54mFrom Code to Customer
42mCONTINUOUS DELIVERY FOR RUBYISTS
32mContinuous Delivery as a Service