Repository navigation
Conversation
…CI scope Split the control-plane Website suite across three runners. Each shard builds and starts the same runtimes; only the test list is divided. Move the always-run guard suites from the CI scope job into a new CI guards job. Every scoped job waits for CI scope, so it now carries only scope detection. CI — required and all production deploys require CI guards.
blove
enabled auto-merge
November 18, 2026 02:34
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
1.
Website — e2e (control-plane)runs as three shards. It is the longest job on a small PR (15.0 to 16.7 min). Each shard builds and starts the same runtimes; only the test list is divided (--shard=n/3).playwright --listlocally: 371 tests unsharded, 124 + 124 + 123 across the shards.2. The guard suites move from
CI scopeto a newCI guardsjob. Every scoped job waits forCI scope, and about 50 s of it was guard tests (Test CI scope classifier, the Debug static preflight,Validate CI workflow guards).CI scopenow does scope detection only.What stays the same
CI — requiredneedsCI guardsand fails unless it succeeds, on PRs and merge-queue candidates.Deploy → Vercel,Canonical demo → VercelandAG-UI demo → VercelneedCI guards; the twoalways()deploys check its result explicitly.Behaviour change to be aware of
A guard failure used to stop every other job from starting. Now the other jobs run and the gate fails at the end. Coverage is the same; a run with a broken guard spends more runner time before failing.
Cost
Two more runners per run that selects Website e2e, and roughly 17 more execution minutes, because each shard repeats about 8.5 min of setup (install, Chromium, builds, server startup).
Expected effect, to be measured on this PR's run
CI scope: about 50 s shorter.Verification
node --test scripts/ci-workflow.spec.mjs: 202 pass, including new contracts for the guards job, the gate, the deploys and the shard divisor.npx nx test scripts: pass.ag-ui-a2ui-configuration,ag-ui-client-tools-preparation,cockpit-matrix,toolchain-policyspecs: pass.scripts/ci-scope.spec.mjsstalls on this macOS machine partway through (325 passed, none failed before the stall); the one test edited here passes on its own. The full list runs in this PR'sCI guardsjob.actionlint: no new findings.🤖 Generated with Claude Code