Episode
How GitLab Built a Single Codebase for One Million CI Pipelines
- Published
- Jun 25, 2026
- Duration seconds
- 458
- Processing state
not_requested
Actions
POST https://stenobird.com/v1/public/podcasts/the-cto-podcast-with-fexingo-technical-leadership-architecture-and-engineering-org-7871807/episodes/how-gitlab-built-a-single-codebase-for-one-million-ci-pipelines/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/the-cto-podcast-with-fexingo-technical-leadership-architecture-and-engineering-org-7871807/how-gitlab-built-a-single-codebase-for-one-million-ci-pipelines.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
In this episode, Lucas and Luna dive into the specific technical decisions GitLab made to scale its CI/CD platform from tens of thousands of pipelines to over one million per day. They focus on the choice of a monolithic application architecture, the use of PostgreSQL partitioning and Redis Cluster, and the trade-offs around job scheduling and queue management. The discussion highlights how GitLab avoided microservice complexity early on and instead optimized a single codebase to handle massive parallel workloads. Listeners will learn about the concept of 'fleet-wide coordination' and how GitLab's engineering team used feature flags and gradual rollout to maintain reliability during rapid growth. This is a concrete case study in scaling developer tools without rewriting everything. #GitLab #CICD #PipelineScaling #MonolithArchitecture #PostgreSQL #RedisCluster #JobScheduling #FeatureFlags #DeveloperTools #ContinuousIntegration #ContinuousDeployment #EngineeringCulture #TechnicalLeadership #BusinessAndTechnology #DevOps #Scale #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo