Skip to content

ADR-005: CI variable surface - #74

Open
UltraBob wants to merge 2 commits into
2.xfrom
adr/ci-variable-surface
Open

ADR-005: CI variable surface#74
UltraBob wants to merge 2 commits into
2.xfrom
adr/ci-variable-surface

Conversation

@UltraBob

@UltraBob UltraBob commented Sep 4, 2026

Copy link
Copy Markdown
Owner

Summary

  • Adopt SKIP_* and _*_ALLOW_FAILURE variables from .gitlab-ci.yml
  • Per-tool variables take precedence over _ALL_VALIDATE_ALLOW_FAILURE
  • Variables honoured only when .gitlab-ci.yml contains Drupal template variable patterns (presence-detected, not mode-gated per ADR-001)
  • Site projects with non-Drupal CI pipelines are unaffected

Review checklist

  • Is the presence-detection approach (check for Drupal template patterns in .gitlab-ci.yml) workable?
  • Are there edge cases where the detection heuristic would get it wrong?
  • Does per-tool precedence over the blanket flag match your current implementation?

Adopt SKIP_* and _*_ALLOW_FAILURE from .gitlab-ci.yml with presence
detection instead of mode gating. Per-tool variables take precedence
over the blanket allow-failure flag.

Review order 5 of 10.
@UltraBob

UltraBob commented Sep 4, 2026

Copy link
Copy Markdown
Owner Author

@mandclu this one should be easy, it is adopting your approach wholesale

@mandclu

mandclu commented Sep 4, 2026

Copy link
Copy Markdown

IIRC my goal was really to honor the variable exactly the way Gotlab CI does. If this proposes adopting the approach of ddev-module-developer that great, but ultimately the goal should always be to match the behavior of Gotlab CI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants