
10/18/2019 · Chrissie Buchanan
What this post added
This post contrasts the complexity and silo-inducing nature of Jenkins' plugin-based architecture with GitLab CI/CD's single-application approach. It details Jenkins' challenges: maintaining build environments, risky upgrades, difficult Groovy maintenance, and lack of clustering. It argues that this complexity leads to knowledge gaps and a 'throw it over the wall' dynamic. The post then positions GitLab CI/CD as a solution that integrates SCM, issue tracking, security testing, and monitoring within a single interface, thereby improving visibility and fostering better DevOps practices.