Build: NX Cloud vs CircleCI evaluation experiment#34567
Closed
kasperpeulen wants to merge 1 commit into
Closed
Conversation
- evaluate-ci.ts: compare NX Cloud vs CircleCI across flakiness, speed, and cost using real API data with SQLite caching - retrigger-ci.ts: staggered cache-busting push script for collecting evaluation data across branches - Add ci-eval.db to gitignore
|
View your CI Pipeline Execution ↗ for commit eb2f81d
☁️ Nx Cloud last updated this comment at |
Member
Author
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.
Closes #
What I did
Run a controlled experiment comparing NX Cloud vs CircleCI on identical workloads to evaluate flakiness, speed, and cost.
Key changes (on
kasper/nx-ai):NX_EXPERIMENTflag to CircleCI config — disables chromatic, benchmark, Windows, and init-empty jobs that aren't ported to NXlinux-browsers-jsagents fromextra_large+tomedium+(4x cost reduction)react-vitest-3→ci:merged,yarn-pnp→ci:dailycancel-in-progress: falseto GH Actions concurrencyThis PR adds (on top of
kasper/nx-ai):evaluate-ci.ts— comparison dashboard script with SQLite cachingmedium+agents fornextbranch reference data--report-onlyfor instant cached reports,--show-runsfor per-run detailretrigger-ci.ts— staggered cache-busting script for collecting 20+ runs per workflow type across 4 eval PRsEvaluation PRs (targeting
kasper/nx-ai):ci:normalci:mergedci:daily(fix sidebar - content float issue #1)ci:daily(Add support for custom webpack config #2)Early results from
nextbranch (100 merged runs):NX Cloud with
medium+agents would be 36% cheaper, 4x faster, and 10x less flaky.Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
Run the evaluation script to verify data collection:
source ~/.config/secrets.shyarn jiti scripts/evaluate-ci.ts --workflow "next:merged" --limit 10 --show-runsDocumentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal,ci:mergedorci:dailyGH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli-storybook/src/sandbox-templates.tsMake sure this PR contains one of the labels below:
Available labels
build: Internal-facing build tooling & test updates. Will not show up in release changelog.🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/coreteam here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>