@@ -12,28 +12,28 @@ The CI runs on every push to `main` and every pull request. It uses smart scopin
12121313## Job Overview
141415-| Job | Purpose | When it runs |
16-| -------------------------------- | -------------------------------------------------------------------------------------------- | ----------------------------------- |
17-| `preflight` | Detect docs-only changes, changed scopes, changed extensions, and build the CI manifest | Always on non-draft pushes and PRs |
18-| `security-scm-fast` | Private key detection and workflow audit via `zizmor` | Always on non-draft pushes and PRs |
19-| `security-dependency-audit` | Dependency-free production lockfile audit against npm advisories | Always on non-draft pushes and PRs |
20-| `security-fast` | Required aggregate for the fast security jobs | Always on non-draft pushes and PRs |
21-| `build-artifacts` | Build `dist/` and the Control UI once, upload reusable artifacts for downstream jobs | Node-relevant changes |
22-| `checks-fast-core` | Fast Linux correctness lanes such as bundled/plugin-contract/protocol checks | Node-relevant changes |
23-| `checks-fast-contracts-channels` | Sharded channel contract checks with a stable aggregate check result | Node-relevant changes |
24-| `checks-node-extensions` | Full bundled-plugin test shards across the extension suite | Node-relevant changes |
25-| `checks-node-core-test` | Core Node test shards, excluding channel, bundled, contract, and extension lanes | Node-relevant changes |
26-| `extension-fast` | Focused tests for only the changed bundled plugins | When extension changes are detected |
27-| `check` | Sharded main local gate equivalent: prod types, lint, guards, test types, and strict smoke | Node-relevant changes |
28-| `check-additional` | Architecture, boundary, extension-surface guards, package-boundary, and gateway-watch shards | Node-relevant changes |
29-| `build-smoke` | Built-CLI smoke tests and startup-memory smoke | Node-relevant changes |
30-| `checks` | Remaining Linux Node lanes: channel tests and push-only Node 22 compatibility | Node-relevant changes |
31-| `check-docs` | Docs formatting, lint, and broken-link checks | Docs changed |
32-| `skills-python` | Ruff + pytest for Python-backed skills | Python-skill-relevant changes |
33-| `checks-windows` | Windows-specific test lanes | Windows-relevant changes |
34-| `macos-node` | macOS TypeScript test lane using the shared built artifacts | macOS-relevant changes |
35-| `macos-swift` | Swift lint, build, and tests for the macOS app | macOS-relevant changes |
36-| `android` | Android build and test matrix | Android-relevant changes |
15+| Job | Purpose | When it runs |
16+| -------------------------------- | -------------------------------------------------------------------------------------------- | ------------------------------------ |
17+| `preflight` | Detect docs-only changes, changed scopes, changed extensions, and build the CI manifest | Always on non-draft pushes and PRs |
18+| `security-scm-fast` | Private key detection and workflow audit via `zizmor` | Always on non-draft pushes and PRs |
19+| `security-dependency-audit` | Dependency-free production lockfile audit against npm advisories | Always on non-draft pushes and PRs |
20+| `security-fast` | Required aggregate for the fast security jobs | Always on non-draft pushes and PRs |
21+| `build-artifacts` | Build `dist/` and the Control UI once, upload reusable artifacts for downstream jobs | Node-relevant changes |
22+| `checks-fast-core` | Fast Linux correctness lanes such as bundled/plugin-contract/protocol checks | Node-relevant changes |
23+| `checks-fast-contracts-channels` | Sharded channel contract checks with a stable aggregate check result | Node-relevant changes |
24+| `checks-node-extensions` | Full bundled-plugin test shards across the extension suite | Node-relevant changes |
25+| `checks-node-core-test` | Core Node test shards, excluding channel, bundled, contract, and extension lanes | Node-relevant changes |
26+| `extension-fast` | Focused tests for only the changed bundled plugins | Pull requests with extension changes |
27+| `check` | Sharded main local gate equivalent: prod types, lint, guards, test types, and strict smoke | Node-relevant changes |
28+| `check-additional` | Architecture, boundary, extension-surface guards, package-boundary, and gateway-watch shards | Node-relevant changes |
29+| `build-smoke` | Built-CLI smoke tests and startup-memory smoke | Node-relevant changes |
30+| `checks` | Remaining Linux Node lanes: channel tests and push-only Node 22 compatibility | Node-relevant changes |
31+| `check-docs` | Docs formatting, lint, and broken-link checks | Docs changed |
32+| `skills-python` | Ruff + pytest for Python-backed skills | Python-skill-relevant changes |
33+| `checks-windows` | Windows-specific test lanes | Windows-relevant changes |
34+| `macos-node` | macOS TypeScript test lane using the shared built artifacts | macOS-relevant changes |
35+| `macos-swift` | Swift lint, build, and tests for the macOS app | macOS-relevant changes |
36+| `android` | Android build and test matrix | Android-relevant changes |
37373838## Fail-Fast Order
3939@@ -42,7 +42,7 @@ Jobs are ordered so cheap checks fail before expensive ones run:
42421. `preflight` decides which lanes exist at all. The `docs-scope` and `changed-scope` logic are steps inside this job, not standalone jobs.
43432. `security-scm-fast`, `security-dependency-audit`, `security-fast`, `check`, `check-additional`, `check-docs`, and `skills-python` fail quickly without waiting on the heavier artifact and platform matrix jobs.
44443. `build-artifacts` overlaps with the fast Linux lanes so downstream consumers can start as soon as the shared build is ready.
45-4. Heavier platform and runtime lanes fan out after that: `checks-fast-core`, `checks-fast-contracts-channels`, `checks-node-extensions`, `checks-node-core-test`, `extension-fast`, `checks`, `checks-windows`, `macos-node`, `macos-swift`, and `android`.
45+4. Heavier platform and runtime lanes fan out after that: `checks-fast-core`, `checks-fast-contracts-channels`, `checks-node-extensions`, `checks-node-core-test`, PR-only `extension-fast`, `checks`, `checks-windows`, `macos-node`, `macos-swift`, and `android`.
46464747Scope logic lives in `scripts/ci-changed-scope.mjs` and is covered by unit tests in `src/scripts/ci-changed-scope.test.ts`.
4848CI workflow edits validate the Node CI graph plus workflow linting, but do not force Windows, Android, or macOS native builds by themselves; those platform lanes stay scoped to platform source changes.
@@ -54,6 +54,7 @@ Local changed-lane logic lives in `scripts/changed-lanes.mjs` and is executed by
5454On pushes, the `checks` matrix adds the push-only `compat-node22` lane. On pull requests, that lane is skipped and the matrix stays focused on the normal test/channel lanes.
55555656The slowest Node test families are split or balanced so each job stays small: channel contracts split registry and core coverage into six weighted shards total, bundled plugin tests balance across six extension workers, auto-reply runs as three balanced workers instead of six tiny workers, and agentic gateway/plugin configs are spread across the existing source-only agentic Node jobs instead of waiting on built artifacts. Broad browser, QA, media, and miscellaneous plugin tests use their dedicated Vitest configs instead of the shared plugin catch-all. The broad agents lane uses the shared Vitest file-parallel scheduler because it is import/scheduling dominated rather than owned by a single slow test file. `runtime-config` runs with the infra core-runtime shard to keep the shared runtime shard from owning the tail. `check-additional` keeps package-boundary compile/canary work together and separates it from runtime topology gateway/architecture work; the boundary guard shard runs its small independent guards concurrently inside one job, and the gateway watch regression uses the minimal `gatewayWatch` build profile instead of rebuilding the full CI artifact sidecar set.
57+`extension-fast` is PR-only because push runs already execute the full bundled plugin shards. That keeps changed-plugin feedback for reviews without reserving an extra Blacksmith worker on `main` for coverage already present in `checks-node-extensions`.
57585859GitHub may mark superseded jobs as `cancelled` when a newer push lands on the same PR or `main` ref. Treat that as CI noise unless the newest run for the same ref is also failing. Aggregate shard checks use `!cancelled() && always()` so they still report normal shard failures but do not queue after the whole workflow has already been superseded.
5960The CI concurrency key is versioned (`CI-v6-*`) so a GitHub-side zombie in an old queue group cannot indefinitely block newer main runs.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。