Back to catalog / Developer tools
GitLab CI/CD pipelines and caching
Configure staged GitLab pipelines, caching, and runners, then verify build and test results.
Skills
Map the project language, lockfiles, tests, and artifacts before designing validate/build/test/deploy stages and job dependencies. Cache reusable downloads with deliberate keys and invalidation; account for runner concurrency and retain failure logs while shortening the critical path. Keep deploy credentials in protected variables and use merge-request pipelines for validation; production environments and triggers need separate approval.
Permissions
Prerequisites
- Requires a GitLab project, known build/test commands, and runner scope; deploy credentials must be configured separately.
Permissions
- May inspect or edit `.gitlab-ci.yml`; pipeline runs consume runner resources and deploy jobs may change external environments.
Limitations
Bad cache keys can reuse stale dependencies; never expose secrets in logs, caches, or unprotected variables.
Pinned upstream source
- Repository
- wshobson/agents
- File path
- plugins/cicd-automation/skills/gitlab-ci-patterns/SKILL.md
- Pinned commit
46891e7e60da0e52baf1050b7b6391b64e84c6d9- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
GitLab CI · Claude Code · compatible coding agents
Main topic
Take a coding Agent change from context to verification