Przejdź do treści
Biblioteka skilli
DevOps i chmura · Budowanie i kod

gitlab-ci

/gitlab-ci

Pomaga pisać i debugować pipeline'y GitLab CI/CD w .gitlab-ci.yml, na przykład dla projektu Drupal z phpcs, phpstan, phpunit, wdrożeniem drush, etapami, regułami i artefaktami.

Repozytorium
claude-plugins ↗
Licencja
MIT
Ostatnia zmiana repozytorium
26.09.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
3
Przestarzałość

Brak sygnałów. Repozytorium zmienione 26.09.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Pomaga pisać i debugować pipeline'y GitLab CI/CD w .gitlab-ci.yml, na przykład dla projektu Drupal z phpcs, phpstan, phpunit, wdrożeniem drush, etapami, regułami i artefaktami.

Wyzwalacze z opisu

add a CI pipeline for this Drupal projectrun phpcs/phpstan/phpunit in GitLab CIdeploy with drush from a pipelinewhy is my job not runningcache composer dependencies
Oryginalny opis (EN)

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.

Jak działa

  1. Pipeline anatomy
  2. Controlling when jobs run — rules:
  3. Drupal test jobs
  4. Deploying with drush
  5. Reuse — include and needs
  6. Troubleshooting
Sekcje z nagłówków SKILL.md, w oryginale · 157 linii, 598 słów
Podgląd SKILL.md
---
name: gitlab-ci
description: >
  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.
---

# 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 | `if: $CI_PIPELINE_SOURCE == "merge_request_event"` |
| Default branch only | `if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH` |
| Tags only | `if: $CI_COMMIT_TAG` |
| Skip on draft MRs | `if: $CI_MERGE_REQUEST_TITLE =~ /^Draft:/` + `when: never` |
| Manual gate | `when: manual` (e.g. production deploy) |

---

## Drupal test jobs

```yaml
phpstan:
  stage: test
  script:
    - composer install --no-progress
    - vendor/bin/phpstan analyse web/modules/custom

phpunit:
  stage: test
  services:
    - name: mariadb:11.4
      alias: db
  variables:
    MARIADB_DATABASE: drupal_test
    MARIADB_ROOT_PASSWORD: root
    SIMPLETEST_DB: mysql://root:root@db/drupal_test
    SIMPLETEST_BASE_URL: http://localhost
  script:
    - composer install --no-progress
    - vendor/bin/phpunit -c web/core/phpunit.xml.dist web/modules/custom
  artifacts:
    when: always
    reports:
      junit: junit.xml          # test results shown in MR widget
```

`services:` starts sidecar containers (database, redis) reachable by alias.

---

## Deploying with drush

```yaml
deploy_prod:
  stage: deploy
  environment:
    name: production
    url: https://www.example.com
  rules:
    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
      when: manual              # require a human click for prod
  script:
    - eval $(ssh-agent -s)
    - echo "$SSH_PRIVATE_KEY" | tr -d '\r' | ssh-add -
    - ssh deploy@prod.example.com "cd /var/www/site && git pull --ff-only
        && composer install --no-dev --optimize-autoloader
        && vendor/bin/drush deploy -y"
```

`drush deploy` runs `updb → config:import → cache:rebuild` in the right
order. Store `SSH_PRIVATE_KEY` as a **masked, protected** CI/CD variable
(Settings → CI/CD → Variables) — never in the repository.

`environment:` makes deployments visible under Operations → Environments and
enables rollback tracking.

---

## Reuse — include and needs

```yaml
include:
  - local: .gitlab/ci/common.yml                  # split big configs
  - component: gitlab.com/components/sast/sast@main   # CI/CD component

phpunit:
  needs: ["phpcs"]      # DAG: start as soon as phpcs passes, skip stage wait
```

`needs:` builds a directed acyclic graph so independent jobs don't wait for
their whole previous stage.

---

## Troubleshooting

| Symptom | Fix |
|---|---|
| Job never appears in pipeline | A `rules:` entry filtered it out — check `$CI_PIPELINE_SOURCE` for the trigger type |
| "This job is stuck" | No runner with matching `tags:`; check runner availability |
| Composer re-downloads everything each run | Cache key/path mismatch — cache `vendor/` and `$COMPOSER_CACHE_DIR`, key on `composer.lock` |
| PHPUnit cannot connect to DB | Service alias must match host in `SIMPLETEST_DB`; wait for DB startup or use healthcheck-aware images |
| Masked variable prints as `[MASKED]` but auth fails | Variable contains newline/CR — for SSH keys use `tr -d '\r'` and file-type variables |
| Pipeline runs twice per MR push | Branch + MR pipelines both enabled — use `workflow: rules:` to keep one |

Wersje

RepozytoriumWynikLicencja
Ta strona · siva01c/claude-plugins100MIT
G1Joshi/Agent-Skills100MIT
dkbnull/hello-skill90MIT

Migawka bazy z 13.11.2026 · wersja paczki 6cf80ee4c533 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100github-actions
    Pomaga pisać i debugować workflow GitHub Actions, na przykład CI dla projektu Drupal z phpcs, phpstan i phpunit, cache composera i wdrożeniem przez SSH.
  • 100ci-cd-gitlab-ci-pipelines
    Buduje wieloetapowe pipeline'y CI/CD w pliku .gitlab-ci.yml, z etapami integracji i wdrożenia.
  • 100gitlab-ci-patterns
    Dostarcza wzorce potoków GitLab CI/CD: etapy, zadania, artefakty, cache i wdrożenia do środowisk, przy pracy z plikiem .gitlab-ci.yml.
  • 90gitlab-ci-handbook
    Wyjaśnia i przegląda pipeline'y GitLab CI/CD, w tym pliki .gitlab-ci.yml, reguły, cache, artefakty i wdrożenia.
  • 90gitlab:ci-monitor
    Obserwuje GitLab CI i bada przyczyny awarii pipeline'ów, czeka na zielony build oraz pomaga pisać i walidować plik .gitlab-ci.yml.
  • 95gitlab-ci-generator
    Tworzy pliki .gitlab-ci.yml: konfiguruje etapy pipeline'u, zadania CI, runnery i wdrożenia oraz generuje szablony GitLab CI/CD według aktualnych dobrych praktyk i standardów bezpieczeństwa.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.