Using GitLab CI/CD only:changes to Run Jobs Only When Relevant Files Change
Learn how GitLab CI/CD's only:changes keyword skips jobs unless specified files are modified, with a working .gitlab-ci.yml example, limits, and verification steps.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how GitLab CI/CD's only:changes keyword skips jobs unless specified files are modified, with a working .gitlab-ci.yml example, limits, and verification steps.
GitLab CI artifacts accumulate by default, inflating repo size and slowing fetches. Learn how to set expiration via UI or YAML, handle version differences, and verify cleanup.
GitLab CI artifacts are kept forever unless you set artifacts: expire_in. Learn how to configure per-job retention, avoid common mistakes, and verify cleanup actually happens.
A step‑by‑step walkthrough for setting minimum approvals, using CODEOWNERS, and verifying the merge gate in GitLab.
Two pipelines, one production environment: how GitLab's resource_group keyword serializes deploy jobs, plus the trade-offs and limits to know first.
Stop letting one slow build job block your entire test suite. Learn how to use GitLab's 'needs' keyword to implement Directed Acyclic Graphs (DAGs) for faster CI/CD execution.
A diagnostic guide to resolving 'stuck' or 'pending' GitLab CI/CD jobs, covering tag mismatches, network connectivity, and config.toml optimizations.
Learn how Gitter automatically maps GitHub or GitLab repository access to chat room roles, the steps to set it up, and the trade‑offs you should consider before relying on this feature.
Your GitLab pipeline has a cache block but reinstalls everything every run. Learn to read the cache lines in job logs, match symptoms to causes, and fix keys, paths, and runner storage.