Skip to content

ci: generate the GitLab pipeline file from the lane contract (Closes #13941) - #13993

Merged
gHashTag merged 4 commits into
masterfrom
lane/gitlab-ci-13941-a
Nov 15, 2026
Merged

gHashTag merged 4 commits into
masterfrom
lane/gitlab-ci-13941-a

Conversation

@gHashTag

@gHashTag gHashTag commented Nov 15, 2026 •

Copy link
Copy Markdown
Collaborator

Refs #13941

The GitLab pipeline file is now generated from the lane contract, never hand-written.

  • specs/ci/gitlab_lane.t27: gl_pipeline_yaml(out) -> u32 renders .gitlab-ci.yml. Stage names come from the new GS_NAMES table (indexed by GS_*), jobs from GL_KINDS / GL_KIND_NAMES (one job per job kind, 12 jobs, 6 stages).
  • Render (NOT committed in this PR; delivered to the GitLab config repo outside the mirrored tree): produced by t27c gen-text specs/ci/gitlab_lane.t27 --fn gl_pipeline_yaml -o .gitlab-ci.yml (4062 bytes). Drift check: git diff --exit-code -- .gitlab-ci.yml after regeneration.
  • FR-003: every job has tags: vps-docker-1g and a rule that never runs fork merge-request pipelines. Assumption: the tag equals the runner description from docs/lab/gitlab_runner.md (GL_RUNNER_TAG); tags are set at registration, which is owner-side.
  • FR-004 / FR-007: no job merges, approves, pushes or edits a seal; the seal jobs only name the CI seal-coverage artifact as input; no secret value, variables are named only.
  • FR-005: the 5 heavy kinds (gl_kind_heavy) check for GL_FREE_GIB_MIN (8 GiB, 8388608 KiB) free disk in before_script.
  • FR-006: 8 new spec tests (determinism, header, 6 stages in order, one job per kind, tag and fork rule on every job, disk check only on heavy kinds, no forbidden words, pinned length 4062 and fingerprint 94383, each with a negative control).
  • Job scripts are print-only (echo job=<kind> commit=$CI_COMMIT_SHA); real gate commands are a follow-up.

Evidence (VPS agent-loop queue, task gl-13941e/f): gen-text renders 4062 bytes; zig test over the t27c gen output passed the other 31 spec tests and gave the pinned fingerprint from the real render; the VPS t27c test-report is BLOCKED on an old-binary array-init lowering (not a spec failure), so the CI test report is the authority. No seal is committed: it comes only from the CI seal-coverage artifact.

🤖 Generated with Claude Code

gHashTag and others added 3 commits November 15, 2026 21:55
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-11-15 15:10:24 UTC

Summary

Status Count
Total Open PRs 49
PRs with Failing Checks 45
PRs with All Checks Green 4
READY 0
FAILING 45
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 45 + 0 + 0 = 45, and there are 49 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=29c50ada25c9 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-11-15 15:11:31 UTC

Summary

Status Count
Total Open PRs 49
PRs with Failing Checks 45
PRs with All Checks Green 4
READY 0
FAILING 45
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 45 + 0 + 0 = 45, and there are 49 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=29c50ada25c9 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit 90dc5d7 into master Nov 15, 2026
37 of 39 checks passed
@gHashTag
gHashTag deleted the lane/gitlab-ci-13941-a branch November 15, 2026 15:13
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.

1 participant