r/gitlab
How We Slashed Our Windows CI/CD Pipeline from 14 Minutes to Under 3 🚀
- upvotes
- 0
- comments
- 0
Post
Highlighted: the lines this signal was extracted from
https://gitlab.com/jakubrojicek11/sentinel-ir-mcp/-/blob/09b61d9dc1b90f3ebc7a37be0493d951249453cf/.github/workflows/windows.yml Waiting 14 minutes for a Windows CI job kills developer flow. For our Model Context Protocol server (Sentinel-IR-MCP), we refused to tolerate that bottleneck anymore. Here is exactly how we optimized our Windows test suite across Node 20, 22, and 24, dropping the total job runtime to 2 minutes and 44 seconds without sacrificing a single check. Source (GitLab, Apache-2.0): https://gitlab.com/jakubrojicek11/sentinel-ir-mcp Package (npm): https://www.npmjs.com/package/sentinel-ir-mcp The analyzer behind it: https://www.npmjs.com/package/sentinel-ir The Bottleneck (GitLab Shared Windows Runners) A standard run on GitLab SaaS Windows took 13.6 minutes, even though our 118 unit tests executed in just 1.6 minutes. The rest was pure infrastructure drag: • VM Provisioning: 3.5 minutes (unfixable) • Real-time Antivirus: Windows Defender choked on npm ci and execution scripts, dragging out our compat-smoke test to 2.9 minutes. The Fix: Strategic Split & Target Optimization Instead of fighting the slow runner environment, we re-architected where and how the jobs run: Shifted Dev Push Matrices to GitHub Actions: GitHub's windows-latest images spin up in seconds (1–2 s) instead of minutes. Built-in Security Clearance: Real-time scanning...
Keep reading with a free account
The rest of this post, and every signal for GitLab, is in your free account.