docs(adr-0028): accept CI/CD + git hosting migration to GitLab
CI / scan (pull_request) Successful in 3m2s
CI / commits (pull_request) Successful in 3m12s
CI / check (pull_request) Successful in 3m23s
CI / a11y (pull_request) Successful in 3m10s
Docs site / build (pull_request) Successful in 3m44s
CI / perf (pull_request) Successful in 6m27s
CI / scan (pull_request) Successful in 3m2s
CI / commits (pull_request) Successful in 3m12s
CI / check (pull_request) Successful in 3m23s
CI / a11y (pull_request) Successful in 3m10s
Docs site / build (pull_request) Successful in 3m44s
CI / perf (pull_request) Successful in 6m27s
ADR-0028 shipped as proposed in #226. No open questions on drivers, considered options, or the 4-phase migration sequence - promote to accepted to unblock Phase 1 (mirror-and-bootstrap). ADR-0015 gets a status-update blockquote at the top calling out that the platform choice "Gitea Actions" is superseded by ADR-0028 while the architectural principles in the rest of ADR-0015 (trunk-based + squash, all-gates-blocking, thin YAML, on-prem runners, signed commits, Conventional Commits) carry over unchanged. ADR-0015's frontmatter status stays accepted - this is the canonical MADR way to handle partial supersession without rewriting the decision record. CLAUDE.md CI/CD architecture bullet rewritten to reflect the accepted-but-not-yet-implemented state. Roll-up bumped to 0001 -> 0028 accepted. Side-fix: the bullet referenced a non-existent `ci:scan` script; replaced with the real names (ci:catalogue-drift, ci:audit, ci:perf, ci:gzip-budgets). No code changes, no ci:check impact.
This commit is contained in:
@@ -7,6 +7,8 @@ tags: [infrastructure, process]
|
||||
|
||||
# CI/CD pipeline — Gitea Actions, trunk-based + squash-merge, thin YAML over portable scripts
|
||||
|
||||
> **Status update — 2026-05-26.** The platform choice **"Gitea Actions"** in §"Decision Outcome" below is superseded by [ADR-0028](0028-migrate-cicd-and-git-hosting-to-gitlab.md) — migration to GitLab CE on `vm-gitlab` accepted, 4-phase rollout in progress. The architectural principles in the rest of this ADR (trunk-based + squash-merge, branch protection, all CI gates blocking, **thin YAML over portable scripts**, on-prem runners, Conventional Commits double-check, signed commits) **carry over unchanged**. This ADR's frontmatter status stays `accepted`; only the platform implementation shifts.
|
||||
|
||||
## Context and Problem Statement
|
||||
|
||||
The repository currently lives on Gitea (`gitea@git.unespace.com:julien/apf_portal.git`). The organisation plans to migrate to GitLab on a 6–18-month horizon. The pipeline shape we adopt now must be (a) operational on Gitea immediately, (b) low-cost to migrate later, and (c) consistent with the project's anti-bricolage and security-first values.
|
||||
|
||||
Reference in New Issue
Block a user