Skip to content

docs(ci): describe CI as the job set behind the rollup check (RIG-5280) - #2222

Merged
mattwilkinsonn merged 1 commit into
compass-comms/rig-2908-testing-tiers-docfrom
compass-comms/rig-5280-build-ci-doc
Oct 12, 2026
Merged

mattwilkinsonn merged 1 commit into
compass-comms/rig-2908-testing-tiers-docfrom
compass-comms/rig-5280-build-ci-doc

Conversation

@rigel-mintaka

@rigel-mintaka rigel-mintaka commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

This PR is part of a stack containing 3 PRs:

  1. main
  2. test(e2e): embedded-postgres smoke leg and WithEmbeddedPostgres (RIG-2906) #2211
  3. docs(testing): document the Go testing tiers (RIG-2908) #2221
  4. "docs(ci): describe CI as the job set behind the rollup check (RIG-5280)" (this PR)

What

The ## CI section of docs/architecture/build-and-ci.md described one CI job, with the real-Postgres suites as a step in it. ci.yml is now a set of jobs behind one required rollup check. The section now describes:

  • setup and tools/ci-matrix (moon's affected set plus changed-paths flags);
  • the moon (<group>) legs;
  • the special jobs, flag-gated on PRs except e2e, and always run on main and nightly;
  • the pgtest and e2e commands, and COMPASS_REQUIRE_LIVE;
  • the "ran rather than skipped" guards;
  • bun-audit;
  • the affected-vs-full rule;
  • the design-ledger-gate injection.

Other sentences that still assumed one job or moon ci are fixed:

  • Task graph: CI uses setup + moon run <targets>, not moon ci.
  • What CI does not gate: the gtk4 and microvm jobs.
  • The unified release lane: the "ONE-JOB doctrine" line is restated as the rule that still holds, that no workflow lists moon projects.
  • Pre-merge build check: setup selects affected projects; the image build runs in the moon (nix) leg behind rollup; the 90m is the moon job's timeout.

testing-tiers.md links back here for CI jobs. The inbound #publishing-the-agent-image anchor is unchanged.

Stacked on #2221.

Verification

  • Each claim was checked against .github/workflows/ci.yml and pr-base-repoint.yml in three review rounds.
  • rumdl check: clean. eng-docs gather tests: 141 pass.

Spec-impact: none
Ledger-impact: none

Closes RIG-5280

Co-authored-by: Matt Wilkinson matt@rigel.build

The CI section described one job with the real-Postgres suites as a
step. ci.yml now runs setup, a moon matrix leg per concern group, and
peer jobs for pgtest, e2e, microvm, forge, gtk4, darwin and the arm64
pin, behind one required rollup check. The section now says so, with
the pgtest and e2e commands, the skip guards, and the affected-vs-full
rule. testing-tiers.md links back to it for CI jobs.

Co-authored-by: Matt Wilkinson <matt@rigel.build>
@linear-code

linear-code Bot commented Oct 12, 2026

Copy link
Copy Markdown

RIG-5280

@rigel-mintaka

Copy link
Copy Markdown
Contributor Author

Review at head 0d5a9c43: high 0, medium 0, low 0, nit 0

  • Scope: the whole PR, all lenses, 3 rounds. Each claim was checked against ci.yml and pr-base-repoint.yml. Round 1 found 1 high (e2e is not flag-gated; it runs on every PR), 3 medium (stale one-job and moon ci lines in the Task graph, release lane and Pre-merge build check sections) and 7 low. All folded.
  • Round 2 found 1 medium: the base-move re-run is automatic, not by hand. Folded, along with wrapping. Round 3 found 1 cosmetic low, folded.
  • Checks: rumdl is clean. The eng-docs gather tests pass (141). The #publishing-the-agent-image anchor is intact.

@github-actions

Copy link
Copy Markdown

Compass engineering docs preview: https://compass-comms-rig-5280-build.compass-eng-docs.pages.dev

Deployed from compass-comms/rig-5280-build-ci-doc at 0d5a9c4.

Changed pages:

@rigel-mintaka
rigel-mintaka marked this pull request as ready for review October 12, 2026 02:22
@mattwilkinsonn
mattwilkinsonn added this pull request to stack #2240 October 12, 2026 19:17
@mattwilkinsonn
mattwilkinsonn merged commit 05f1603 into main Oct 12, 2026
21 checks passed
@mattwilkinsonn
mattwilkinsonn deleted the compass-comms/rig-5280-build-ci-doc branch October 12, 2026 19:18
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