GitLab CI/CD rewards a little discipline. These are the practices that keep it maintainable as a team and a codebase grow.
The practices
- Use stages and needs: for a fast DAG pipeline
- Cache dependencies and pass build output as artifacts
- Store secrets as masked, protected CI/CD variables
What good looks like
Stages, caching and a manual production gate.
stages: [build, test, deploy]
cache: { paths: [node_modules/] }
build:
stage: build
image: node:20
script: [npm ci, npm run build]
test:
stage: test
image: node:20
script: [npm test]
deploy:prod:
stage: deploy
script: [./deploy.sh]
environment: { name: production }
when: manual
rules: [{ if: '$CI_COMMIT_BRANCH == "main"' }]Anti-patterns to retire
- Everything in one stage, so nothing runs in parallel
- No cache/artifacts config, re-downloading dependencies every job
- Secrets in .gitlab-ci.yml instead of masked/protected CI variables
Want senior help putting GitLab CI/CD to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.