oro-behat-ci
Installation
SKILL.md
OroCommerce v6.1 Behat in CI/CD
Oro's public CI support is Jenkins-only. GitLab CI works but is community territory — the upstream issue oroinc/platform#954 has been open since Oro 2.x with no ETA. This skill consolidates the canonical Jenkins patterns (scattered across oroinc/orocommerce-application, oroinc/docker-build, oroinc/environment) and the community-developed GitLab CI patterns that fill the gap.
Decision: Jenkins or GitLab?
| Situation | Use |
|---|---|
| Greenfield Oro CI, no prior commitment | Jenkins — follow oroinc canonical patterns, lowest maintenance cost |
| Enterprise default is GitLab | GitLab CI in DinD with docker compose up, see references/gitlab-ci.md |
| Small dev-only CI with compose stack already | GitLab with basic compose invocation |
| Need init-image snapshot fast paths | Either — both platforms pull from the same docker-build registry |
Do not attempt GitLab native services: keyword for Oro. It cannot model the compose fanout.
Canonical Formatter Combo
Always run both formatters — pretty for humans tailing logs, junit for the CI report: