Menu

1 / 2

War Story: We Switched From Jenkins 2.440 to GitLab CI 16.10 and Cut Deploy Time by 50%

DEV Community·ANKUSH CHOUDHARY JOHAL·6 months ago
#0AomjOel
#tip#story#switched#jenkins#gitlab
Reading 0:00
15s threshold

At 2:17 PM on a Tuesday, our Jenkins 2.440 pipeline took 42 minutes to deploy a single microservice to production. By 2:17 PM the following Tuesday, our GitLab CI 16.10 pipeline did the same deploy in 21 minutes flat. Here’s how we cut deploy time by 50% with zero unplanned downtime, backed by benchmark data, production code samples, and hard-won lessons from a 12-person engineering team.

📡 Hacker News Top Stories Right Now

GTFOBins (203 points)

Talkie: a 13B vintage language model from 1930 (377 points)

The World's Most Complex Machine (52 points)

Microsoft and OpenAI end their exclusive and revenue-sharing deal (886 points)

Can You Find the Comet?…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.