← ClaudeAtlas

gitlab-cilisted

Use this skill when authoring or debugging GitLab CI/CD pipelines (.gitlab-ci.yml) — e.g. "add a CI pipeline for this Drupal project", "run phpcs/phpstan/phpunit in GitLab CI", "deploy with drush from a pipeline", "why is my job not running", "cache composer dependencies", or anything involving stages, rules, artifacts, environments, or GitLab runners.
siva01c/claude-plugins · ★ 16 · DevOps & Infrastructure · score 78
Install: claude install-skill siva01c/claude-plugins
# GitLab CI/CD Skill GitLab CI runs pipelines defined in `.gitlab-ci.yml` at the repository root. This skill covers pipeline authoring with a Drupal project as the working example: validate → test → build → deploy, with composer caching and drush-based deployment. --- ## Pipeline anatomy ```yaml stages: - validate - test - deploy default: image: php:8.3-cli before_script: - curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer variables: COMPOSER_CACHE_DIR: "$CI_PROJECT_DIR/.composer-cache" cache: key: files: - composer.lock # cache invalidates when the lock file changes paths: - .composer-cache/ - vendor/ ``` - **`stages`** run sequentially; jobs within a stage run in parallel. - **`default`** holds settings shared by all jobs. - **Cache vs artifacts:** cache is best-effort storage between pipelines (composer/npm caches); artifacts pass build results between jobs of the same pipeline and can be downloaded from the UI. --- ## Controlling when jobs run — `rules:` `rules:` replaces the deprecated `only/except`: ```yaml phpcs: stage: validate script: - composer install --no-progress - vendor/bin/phpcs --standard=Drupal,DrupalPractice web/modules/custom rules: - if: $CI_PIPELINE_SOURCE == "merge_request_event" - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH ``` First matching rule wins. Common conditions: | Goal | Rule | |---|---| | MR pipelines only |