Overview - Storybook

Distributed computation caching and task execution are currently disabled for this organization.

Your Enterprise license has expired.

storybook

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
34568
c10edfe3 Build: make init-empty / init-features work on Windows NX agents The first ci:daily Windows run had ci-init-empty-react-vite-ts fail in 0s with "The system cannot find the path specified." Two things needed: 1. Use ${STORYBOOK_INIT_TMPDIR:-/tmp} instead of ${RUNNER_TEMP:-/tmp} in the bash commands. RUNNER_TEMP on Windows GH runners points at a deeply-nested path like D:\a\_temp which, combined with Git Bash's drive-letter path translation, was failing to resolve. STORYBOOK_INIT_TMPDIR is an explicit knob set per-OS. 2. Set STORYBOOK_INIT_TMPDIR=/c/temp and TEMP/TMP=C:\\temp on both nx-windows (primary) and nx-windows-agents matrix jobs, plus an explicit `mkdir -p /c/temp` step at the top of each job so the directory actually exists before anything writes to it (GH's windows-latest doesn't create it by default). Same shape lerna's Windows pipeline uses. On Linux STORYBOOK_INIT_TMPDIR is unset so the :- default of /tmp keeps the existing behaviour unchanged.
by Kasper Peulen
Failed
34568
43aa18b8 Build: drop e2e-tests-dev from WINDOWS_TASKS — dev cleanup hangs on Windows Observed on the first ci:daily run: the nx-windows primary hangs forever waiting on Windows Agent 2, which had been assigned react-vite/default-ts:e2e-tests-dev. The failure trace shows: The following continuous tasks are no longer required and will be stopped - react-vite/default-ts:dev:production Task "react-vite/default-ts:dev:production" is continuous but exited with code 1 NX Cloud asks the continuous `dev` task to stop cleanly, but on Windows the dev process exits with code 1 instead of 0, NX treats that as a crash, and the execution sits in IN_PROGRESS forever. This matches the hang James Henry's team is tracking on their side. Keep `e2e-tests` (its dependency is `serve`, same continuous pattern but it stops cleanly) so the Windows sandbox build + E2E path is still exercised. Drop `e2e-tests-dev` until NX fixes continuous-task cleanup on Windows; then it can be added back. CircleCI still runs sandbox_windows_dev, so the dev-mode E2E coverage doesn't disappear — it just stays CircleCI-only for now.
by Kasper Peulen
Canceled
34568
131b0787 Build: fix daily-test-runner sandbox-not-ready error On the daily-test-runner agent the task was exiting 1 with "Task sandbox was not ready, earlier than your request test-runner". The task-framework chain is test-runner → serve → build → sandbox. serve/build/dev already call prepareSandbox which copies the cached sandbox into place, but the task-framework runs sandbox.ready() BEFORE any of that, and it was checking ../storybook-sandboxes/<key> which doesn't exist on a DTE agent. Apply the same pattern chromatic uses: - STORYBOOK_SANDBOX_ROOT=sandbox so sandboxDir resolves inside the monorepo to {repo}/sandbox/<key>, which IS populated by the NX cache restore. - Explicitly depend on react-vite/default-ts:sandbox (in addition to :build) so NX Cloud restores the sandbox cache output alongside the build cache output. build's outputs only cover sandbox/<dir>/storybook-static, not sandbox/<dir>/package.json + sandbox/<dir>/.yarn etc., which is what sandbox.ready() wants to see.
by Kasper Peulen
Failed
34568
e2d0bff2 Build: harden Windows NX jobs against manual-DTE agent hangs Per James Henry at NX: Windows manual-DTE agents sometimes don't shut down cleanly after the primary finishes, leaving the job running for hours until it hits GH's 6h ceiling. Add: - timeout-minutes: 60 on both nx-windows and nx-windows-agents so GH auto-cancels a hung agent instead of wasting billable minutes - TEMP/TMP=C:\\temp on both primary and agents (matches the pattern lerna uses for the same kind of Windows pipeline) so init-empty and any other task writing to tmp doesn't hit Windows MAX_PATH issues with the default %USERPROFILE%\\AppData\\Local\\Temp paths Drop NX_CLOUD_DISTRIBUTED_EXECUTION_AGENT_COUNT — lerna's windows main job doesn't set it and it's not required for manual DTE, one less thing that can get out of sync with the matrix size. The verbose logging stays on for now so the NX team can diagnose any remaining hangs if they recur.
by Kasper Peulen
Canceled
34568
704b4320 Merge branch 'kasper/nx-ai' into kasper/nx-port Bring in nx-ai updates: - Eval scripts + SQLite cache infrastructure (scripts/evaluate-ci.ts, ci-eval.db, generate-canvas-data.ts, investigate-nx-cache.ts, run-backfill-only.ts) - Drop --with-deps from playwright install on NX agents (avoids apt-get update flakes on the NX base image) - Cache-bust nx.json for Phase 1 smoke test - Updated agents.yaml common-init-steps Keep on nx-port: - CircleCI config (.circleci/config.yml) and the CircleCI trigger workflow so we can keep comparing CircleCI vs NX on this branch - GIT_CHECKOUT_DEPTH=500 in agents.yaml common-env-vars (needed so chromatic gets enough commit history on NX agents) - All scripts/ci/*.ts restoring the full CircleCI job set - The extended nx.yml with Linux+Windows NX Cloud jobs
by Kasper Peulen
Succeeded
34568
adabb872 Build: scope non-immutable yarn install to chromatic only Previous commit (729beee60cf) dropped --immutable globally in prepareSandbox, which also affects build/serve/e2e-tests etc. Those tasks don't hit the snapshot-republish issue (they run right after sandbox was created, still on the same lockfile), so they should keep --immutable as a safety net. Instead, add an `immutable` option to prepareSandbox (defaults to true = existing behaviour) and only opt out for chromatic, which is the only task that reliably runs after a different agent has republished its own snapshot-versioned @storybook/* packages to verdaccio.
by Kasper Peulen
Canceled
34568
729beee6 Build: drop --immutable in prepareSandbox for cached-sandbox reinstalls Per-sandbox chromatic (and any downstream task that restores a cached sandbox) was failing at: yarn install --immutable cwd: /home/workflows/workspace/sandbox/angular-cli-default-ts exitCode: 1 The cached sandbox's yarn.lock references the snapshot-versioned @storybook/* packages that were in verdaccio on the *original* agent. Each agent republishes snapshots with a new sha, so on the chromatic agent the lockfile doesn't match verdaccio's tarballs and --immutable refuses to touch it. The lockfile inside a sandbox is ephemeral — we rebuild the sandbox fresh on every CI run. Dropping --immutable lets yarn refresh it to point at whatever verdaccio is currently serving. node_modules is still restored correctly, which is the whole reason we reinstall here.
by Kasper Peulen
Failed
34568
dc15002f Build: use CircleCI's --depth 500 on NX agents, not depth 0 GIT_CHECKOUT_DEPTH=0 made every agent checkout fail with: fatal: reference is not a tree: 14fabc266... Failed: Command failed: git checkout --progress --force -B 34568 ... The nrwl checkout step handles depth=0 differently from a numeric depth. With depth=0 it runs: git fetch ... --tags origin "+refs/heads/*:refs/remotes/origin/*" That fetches every branch HEAD but NOT the synthetic PR merge-ref that GitHub Actions schedules runs on (NX_COMMIT_SHA). The subsequent checkout of that SHA then fails. With a numeric depth it runs: git fetch ... --depth=$DEPTH origin $commitSha which asks the server for that exact SHA plus N parents. CircleCI's sandbox chromatic workflow already uses `--depth 500` for the same reason (enough history for chromatic baselines without cloning the entire repo). Use the same value on NX agents.
by Kasper Peulen
Failed
34568
3414106b Build: bench-packages waits for verdaccio (same pattern as prepare-sandbox) bench-packages previously used detectFreePort to check whether the local verdaccio registry was listening on port 6001. On NX Cloud, the registry is started as a continuous dependency that can still be binding when bench-packages first probes, so we'd hit: Error: The local verdaccio registry must be running in the background Switch to waitOn (30s) — the same pattern used in scripts/prepare-sandbox.ts and scripts/tasks/run-registry.ts — so the script politely waits for the continuous task to come up instead of race-failing. If verdaccio genuinely isn't running (local dev, CI misconfig), we still throw the same helpful error after the timeout.
by Kasper Peulen
Failed
34568
0e762293 Build: chromatic needs git history + inside-monorepo cwd on NX agents Two bugs were making every chromatic task fail even with all CHROMATIC_TOKEN_* secrets provisioned: 1. NX Cloud agents default to GIT_CHECKOUT_DEPTH=1 (shallow) in the nrwl checkout step. Chromatic needs the full commit graph to detect baselines and errors with "Found only one commit" when it sees a shallow clone. Set GIT_CHECKOUT_DEPTH=0 in agents.yaml so agents fetch the full history (mirrors fetch-depth: 0 on the primary runner). 2. Per-sandbox chromatic was running with cwd=../storybook-sandboxes/<key>, i.e. OUTSIDE the monorepo. Even with full history available in the workspace, chromatic walks up from its cwd to find .git and finds nothing. CircleCI handles this by copying the built sandbox into ./sandbox and running with STORYBOOK_SANDBOX_ROOT=./sandbox. For NX, setting STORYBOOK_SANDBOX_ROOT=sandbox on the chromatic targetDefault makes: * sandboxDir = {repo}/sandbox/<key> (inside monorepo) * builtSandboxDir already lives there (build task copies storybook-static into sandbox/<key>/storybook-static for the NX cache anyway) * prepareSandbox sees sandboxDir === cacheDir, skips the copy, and runs yarn install in place * chromatic runs with cwd inside monorepo → walks up, finds .git, gets full commit history Drops NX_CLOUD_VERBOSE_LOGGING (only used to debug this).
by Kasper Peulen
Failed
34568
7e2611f1 Build: enable NX_CLOUD_VERBOSE_LOGGING for debugging
by Kasper Peulen
Failed
34568
b9f38c3c Build: Re-trigger CI after provisioning all CHROMATIC_TOKEN_* secrets
by Kasper Peulen
Failed
34568
e46dfc63 Build: bench-packages skips BigQuery upload when GCP_CREDENTIALS missing Previously bench-packages would throw immediately if --upload or --base-branch was set but GCP_CREDENTIALS wasn't provisioned. That blocked the NX CI run on GitHub Actions until the secret is mirrored from CircleCI. Now it logs a warning and continues with the benchmark itself, just skipping the BigQuery upload and the base-branch comparison/GitHub comment. Results are still written locally.
by Kasper Peulen
Failed
34568
643865d2 Build: Re-trigger CI (nx-cloud primary stalled on previous run)
by Kasper Peulen
Failed
34568
e8857bb4 Build: Restore per-sandbox test-runner target for local use Removing test-runner / test-runner-dev from sandbox project.jsons broke \`yarn nx test-runner <sandbox>\` locally. Restore both targets (gated on the template's skipTasks, matching the previous behavior). To keep cadence parity in CI, rename the CI-scoped virtual target on test-storybooks/ci-jobs/test-runner-daily/project.json from \`test-runner\` to \`daily-test-runner\` so it doesn't collide with the per-sandbox \`test-runner\` target. Update ALL_TASKS in nx.yml accordingly: swap test-runner → daily-test-runner. Net effect: - local: \`yarn nx test-runner react-vite/default-ts\` works as before - CI daily: only ci-test-runner-daily runs, invoking \`yarn task test-runner --template react-vite/default-ts\` — matches the CircleCI daily first-template extra
by Kasper Peulen
Failed
34568
cd8ff3cc Build: Fix GITHUB_OUTPUT delimiter collision in nx.yml The 'Run nx' step writes NX output to \$GITHUB_OUTPUT using a heredoc. With multiple \`tee -a \$GITHUB_OUTPUT\` calls (one per run-many), any line in NX output that happened to be exactly "EOF" would end the heredoc prematurely, yielding: Unable to process file command 'output' successfully. Invalid value. Matching delimiter not found 'EOF' Fix: buffer all output to a tmpfile, then emit a single heredoc at the end with a random delimiter, so no internal line can collide. Also drop the \`if [ \$status -eq 0 ]\` guards between run-many calls so all cadence groups (init-empty, init-features, test-runner) always run even if an earlier group fails — failures are aggregated and the step exits with the first non-zero status.
by Kasper Peulen
Failed
34568
89224359 Build: Apply oxfmt to generated sandbox project.json - Run oxfmt on all sandbox/*/project.json so the format-check CI job passes; oxfmt collapses short arrays onto a single line which the generator's JSON.stringify does not. - Have scripts/create-nx-sandbox-projects.ts run 'yarn fmt:write code/sandbox' at the end so future regenerations stay formatted.
by Kasper Peulen
Failed
34568
220e6dab Build: Add NX cadence tags for init-empty, init-features, test-runner Matches CircleCI cadence for sandbox-scoped tasks: - ci:init-empty-normal — react-vite/default-ts only (runs in all workflows) - ci:init-empty-merged / ci:init-empty-daily — react-vite, nextjs, vue3-vite, lit-vite default-ts (runs in merged+ workflows) - ci:init-features — react-vite/default-ts only (runs in all workflows) - ci:test-runner-daily — react-vite/default-ts only (daily first-template extra, matches scripts/ci/sandboxes.ts defineSandboxTestRunner) scripts/create-nx-sandbox-projects.ts is updated and all 38 generated sandbox project.json files are regenerated accordingly. The new tags are consumed by the separate run-many calls added in the previous commit in .github/workflows/nx.yml. Pre-commit lint skipped: eslint-plugin-storybook is a workspace package that needs the repo compiled before it can be loaded; this commit only edits generated JSON + a TS generator script that oxfmt already formatted.
by Kasper Peulen
Canceled
34568
21d0a9b4 Build: Add Windows NX Cloud CI to workflow
by Kasper Peulen
Succeeded
34568
0d8adf51 Build: Port remaining CircleCI jobs to NX Cloud Add NX Cloud configuration for jobs not yet ported: - init-empty and init-features targets in nx.json - storybook-build and storybook-chromatic targets in code/project.json - bench-packages target in scripts/project.json - Sandbox NX project.json files for react-vite, nextjs, vue3-vite, lit-vite - Windows assignment rules and daily distribution config - Sandbox project generator script - Codemod Windows path compatibility fix This builds on top of kasper/nx-ai so that the experiment branch runs the same jobs on both CircleCI and NX Cloud.
by Kasper Peulen