Case Study: T-Mobile achieves hundreds of thousands of hours saved and tens of millions in cost savings with CloudBees Core (Jenkins)

Savings Thousands of Hours and Millions of Dollars at T-Mobile with Jenkins

T-Mobile, a major telecommunications provider and growing technology company, faced a scaling and reliability challenge with its Jenkins-based CI/CD platform: a plugin‑heavy, single‑master environment that required frequent restarts and forced developers to act as infrastructure engineers. The SRE team had rolled out phase 1 of their POET pipeline to 30+ teams and needed a stable, scalable solution to support 350 developer teams and ~5,000 users.

They built a containerized, centrally managed POET pipeline on Jenkins and CloudBees Core running in Kubernetes, cut master plugins dramatically (from ~200 to 4, with teams limited to 16 core add-ons), and moved to ~30 masters. Masters can be spun up from Docker in about two minutes, developer ownership replaced infrastructure toil, downtime fell from multiple weekly restarts to roughly one incident per year, and T‑Mobile estimates hundreds of thousands of saved work hours and tens of millions of dollars in cost savings.

T-Mobile

Ravi Prativadi

Manager Software Development