Consolidate ZGW integration checks into one full-stack CI stage #58

New Issue

not · 2026-06-29T14:37:38Z

not commented

2026-06-29 14:37:38 +00:00

On the single self-hosted runner, CI jobs run sequentially, not in parallel. Today the OpenZaak-dependent jobs each boot OpenZaak from scratch — integration (#46), notifications (#56), and compose-smoke each bring up their own stack — so OpenZaak's ~4-min migration boot is paid ~3× in a row.

Outcome: one verify-stack CI job that brings the full compose stack up once and runs, as clearly-named sequential steps:

bring up + wait for health (subsumes compose-smoke's DoD health check),
ACL ↔ OpenZaak integration tests,
OpenZaak → NRC notification delivery,
then tears down (with a log dump on failure).

Approach: extract the check logic into stack-agnostic runners (infra/run-acl-integration.sh, infra/run-notification-check.sh) that operate on whatever stack is already up (reaching services by container IP). The local single-concern targets (make integration oz-only, make verify-notifications oz+nrc) keep working by delegating to the same runners — no logic duplicated.

Out of scope: changing what the checks assert.

Refs #46, #56. Folded into the #56 PR (#57) since it reworks the jobs those introduced.

On the single self-hosted runner, CI jobs run **sequentially**, not in parallel. Today the OpenZaak-dependent jobs each boot OpenZaak from scratch — `integration` (#46), `notifications` (#56), and `compose-smoke` each bring up their own stack — so OpenZaak's ~4-min migration boot is paid ~3× in a row. **Outcome:** one `verify-stack` CI job that brings the **full** compose stack up **once** and runs, as clearly-named sequential steps: 1. bring up + wait for health (subsumes `compose-smoke`'s DoD health check), 2. ACL ↔ OpenZaak integration tests, 3. OpenZaak → NRC notification delivery, then tears down (with a log dump on failure). **Approach:** extract the check logic into stack-agnostic runners (`infra/run-acl-integration.sh`, `infra/run-notification-check.sh`) that operate on whatever stack is already up (reaching services by container IP). The local single-concern targets (`make integration` oz-only, `make verify-notifications` oz+nrc) keep working by delegating to the same runners — no logic duplicated. **Out of scope:** changing what the checks assert. Refs #46, #56. Folded into the #56 PR (#57) since it reworks the jobs those introduced.

not added this to the Iteration 1 — Walking Skeleton milestone 2026-06-29 14:37:38 +00:00

not added the type:chore area:infra labels 2026-06-29 14:37:38 +00:00

not referenced this issue from a commit

2026-06-29 14:48:42 +00:00

refactor(ci): one verify-stack stage for all live-stack checks (closes #58) (refs #46 #56)

not referenced a pull request that will close this issue

2026-06-29 14:48:57 +00:00

feat(infra): wire OpenZaak → Open Notificaties notifications (closes #56) #57

not closed this issue

2026-06-30 12:29:44 +00:00

Sign in to join this conversation.