Overview - Storybook

storybook

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
35352
b9427606 ci: build the sandbox static output inside the create job The standalone (build) job per template was ~90s of which ~55s was fixed setup (spin-up, checkout, workspace attach and unpack) around a ~25-45s build - and it sat between (create) and the e2e/chromatic/vitest jobs on the workflow critical path, adding a full job hop plus a workspace round-trip to those chains. The static build now runs at the end of the create job, before the sandbox is packed, so storybook-static travels inside the existing sandbox tarball and downstream jobs need no extra restore step. e2e, chromatic, vitest and test-runner depend on create directly. The Windows sandbox jobs and the daily test-runner job referenced flow jobs by array index; they now use named references, since the build job no longer exists. saveBench('build') records identical data - it runs inside 'yarn task build' regardless of which CI job hosts it, and no job in the generated workflows consumed the bench task output.
by Valentin P...
V