iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can make a Storybook build available from an Azure DevOps pipeline without deploying it to a website: build its static files, then publish the output folder as a pipeline artifact. Teammates can retrieve or download those files from the run summary, but they will not get a browser-accessible Storybook URL.
What “show Storybook” means without hosting
Storybook builds into a static web application. Publishing its files as an Azure Pipelines artifact attaches them to a pipeline run for retrieval or use by a downstream pipeline; it does not serve the application as a website. Microsoft describes PublishPipelineArtifact@1 as a way to upload a file or directory as a named artifact for the current run.
| Approach | What teammates receive | Separate hosting? | Fits when |
|---|---|---|---|
| Azure Pipelines artifact | Files to inspect or download from a pipeline run | No | Build handoff, archival, or downstream pipeline use |
| Static host or Storybook publishing service | A browser-accessible Storybook URL | Yes | Interactive review by teammates or stakeholders |
Build and publish the Storybook artifact
-
Confirm the repository’s package manager, Storybook build script, and output directory. Storybook’s build documentation uses
npm run build-storybookas the standard command, and its tutorial identifiesstorybook-staticas the output directory. Verify the actual output path configured for your project before adding it to the pipeline.Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteSpecial offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Add a build step followed by an artifact publish step in the build pipeline. This example assumes npm and an npm script named
build-storybook; adapt the install command and script to your repository:#1 Best Overall
steps: - script: npm ci && npm run build-storybook displayName: Build Storybook - publish: storybook-static artifact: storybookOn Azure DevOps Services, the YAML
publishshortcut publishes the specified folder as an artifact namedstorybook. The shortcut is equivalent to using the PublishPipelineArtifact@1 task. -
Run the pipeline, then open the completed run and select its artifact in the run summary to inspect or download the files. The download is the generated build output, not a hosted Storybook page.
Choose the artifact task for your Azure DevOps edition
The YAML shortcut and Pipeline Artifacts are supported in Azure DevOps Services. If you use Azure DevOps Server or TFS 2018, Microsoft says Pipeline Artifacts are not supported there; use Publish Build Artifacts instead. The workflow described here is for a build pipeline: Microsoft’s Pipeline Artifacts documentation says publishing pipeline artifacts is not supported in release pipelines.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Troubleshoot an incomplete artifact
-
The artifact is missing or the publish step fails: Check that the configured Storybook build completed and that the directory named in the publish step exists at that point in the job. Confirm the output path rather than assuming it is
storybook-static. -
Images or other static files are absent: Review the project’s static-file configuration. Storybook supports
staticDirs; Vite projects may also copy files from the Vite public directory. Inspect the generated output to confirm the assets were included. See Storybook’s static assets documentation. -
You need a clickable browser preview: An artifact alone does not provide one. Storybook documents that its static build can be published to a web host; doing so adds hosting. Azure’s Azure Static Web Apps task is a deployment task, not an artifact-only alternative.
Check access and retention in your organization
Artifact publication makes the files available through the pipeline run, but the specific people who can access that run and how long its artifacts remain available depend on your Azure DevOps organization’s permissions and retention settings. Check those policies before relying on an artifact as a long-term archive or sharing route.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
