How Indeed transformed its CI platform with GitLab

What this post added

This post details Indeed's successful migration from Jenkins to GitLab CI. It outlines the technical challenges faced with Jenkins' architecture (single point of failure controllers, manual scaling) and the problems with their previous Groovy Jenkins DSL approach (job duplication, maintenance burden). The post explains the adoption of GitLab CI, highlighting its scalability, cloud-native design, and template extensibility which aligned with their 'golden path' strategy. It describes the migration process, including creating golden path templates for common project types (Java, Python, JavaScript), leveraging InnerSource for contributions to these templates, and employing strategies like 'scream tests' and controller read-only policies to drive adoption. The benefits realized, such as increased pipeline volume, reduced hardware costs, and decreased support burden, are quantified.