Menu

Post image 1
Post image 2
1 / 2
0

We Ditched Jenkins for GitLab CI 16.5: 40% Fewer Security Vulnerabilities

DEV Community·ANKUSH CHOUDHARY JOHAL·about 1 month ago
#YVcSM4wU
Reading 0:00
15s threshold

After 7 years of maintaining 14 Jenkins masters across 3 regions, we migrated 112 microservices to GitLab CI 16.5 in Q3 2024. The result? A 40% reduction in critical security vulnerabilities, 22% faster pipeline execution, and $147k annual savings in idle compute costs. This isn’t a vendor pitch—it’s a benchmark-backed postmortem of a migration that fixed our broken CI/CD security posture. 📡 Hacker News Top Stories Right Now New Integrated by Design FreeBSD Book (21 points) Microsoft and OpenAI end their exclusive and revenue-sharing deal (719 points) Is my blue your blue? (280 points) Talkie: a 13B vintage language model from 1930 (21 points) Three men are facing charges in Toronto SMS Blaster arrests (70 points) Key Insights GitLab CI 16.5’s built-in SAST/DAST integration reduced unpatched CVEs from 217 to 130 per quarter across 112 services, a 40% reduction in critical/high severity vulnerabilities.…

Continue reading — create a free account

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

Read More