🔧 Checking the CI/CD Pipeline
Friday, 4:58 PM
You open .gitlab-ci.yml (or .github/workflows/deploy.yml if you're on GitHub).
Something catches your eye immediately:
build:
image: node:18-alpine
script:
- npm ci
- npm run build
# memory: 2GB <-- This line is commented out!
Wait. Someone commented out the memory limit? You check the blame:
Author: intern-alex
Date: Yesterday
Message: "cleanup: remove unused comments"
The intern. Of course. Thought it was a comment. It wasn't.
The analytics dashboard commit also added a huge dependency. That explains the memory spike.
✅ Fix the YAML and restore memory limits
Uncomment the memory configuration, bump it to 4GB to handle the new dashboard, and redeploy. This is the right fix.
🔄 Just restart the runners
Maybe the runners are just stuck. Hit that restart button and pray. Sometimes it just worksâ„¢.
---
Time elapsed: 11 minutes
You found the smoking gun. Now fix it properly.