Repository navigation
ci: run integration without waiting for build - #40
Conversation
Integration checks out the repo and runs the committed dist/index.mjs. It takes no artifact or output from build, so waiting for build only put Windows integration's setup on the critical path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
Verdict: PASS+NOTES Head SHA: 0d714c8 (independent read-only verification via
|
Why
The goal is CI that gives agents and me a result sooner, changing only what the run history supports. On this repo the integration matrix waits for
build, though it uses nothingbuildproduces. Integration checks out the repo, runsnpm ci, and executes the committeddist/index.mjs.What changed
needs: buildis gone from theintegrationjob, so the three integration legs start alongsidebuild.smoke-testkeeps itsneeds, since it runs only on manual dispatch.Numbers
Measured from the last 41 green PR runs (GitHub API, script kept with the audit):
Windows integration finishes last in 39 of 41 PR runs. Its own work is setup (checkout 5 s, setup-node 5 s,
npm ci7 s) plus a 2 s command, and it starts only afterbuildfinishes.Expected effect, a guess: PR run p50 drops to about 29 s.
How to check it
After merge, compare at least 15 PR runs against the 41-run baseline above. Revert if p50 doesn't drop by at least 10 s.
Left out
🤖 Generated with Claude Code
Summary by CodeRabbit