Docs: Adds Semaphore to CI

chromaui · Jan 16, 2025 · 31e746e · 31e746e
1 parent 994426d
commit 31e746e
Show file tree

Hide file tree

Showing 10 changed files with 614 additions and 17 deletions.
diff --git a/src/content/ci/azure-pipelines.mdx b/src/content/ci/azure-pipelines.mdx
@@ -301,9 +301,9 @@ Chromatic can be run on monorepos that have multiple subprojects. Each subprojec
 #### Prerequisites
 
 1. Ensure that you're in the correct working directory for the subproject.
-2. Have `build-storybook` npm script in the subproject's `package.json` file OR explicitly name the script using the `buildScriptName` parameter and make sure the script is listed in the subproject's `package.json` file.
+2. Have `build-storybook` npm script in the subproject's `package.json` file OR explicitly name the script using the `--build-script-name` CLI flag and make sure the script is listed in the subproject's `package.json` file.
 
-If you've already built your Storybook in a separate CI step, you can alternatively point the action at the build output using the `storybookBuildDir` parameter.
+If you've already built your Storybook in a separate CI step, you can adjust your workflow to include the `--storybook-build-dir` CLI flag to point to the build output directory.
 
 ```yml title="azure-pipelines.yml"
 # Other configurations

diff --git a/src/content/ci/bitbucket-pipelines.mdx b/src/content/ci/bitbucket-pipelines.mdx
@@ -184,9 +184,9 @@ Chromatic can be run on monorepos that have multiple subprojects. Each subprojec
 #### Prerequisites
 
 1. Ensure that you're in the correct working directory for the subproject.
-2. Have `build-storybook` npm script in the subproject's `package.json` file OR explicitly name the script using the `buildScriptName` parameter and make sure the script is listed in the subproject's `package.json` file.
+2. Have `build-storybook` npm script in the subproject's `package.json` file OR explicitly name the script using the `--build-script-name` CLI flag and make sure the script is listed in the subproject's `package.json` file.
 
-If you've already built your Storybook in a separate CI step, you can alternatively point the action at the build output using the `storybookBuildDir` parameter.
+If you've already built your Storybook in a separate CI step, you can adjust your workflow to include the `--storybook-build-dir` CLI flag to point to the build output directory.
 
 ```yml title="bitbucket-pipelines.yml"
 # A sample pipeline implementation

diff --git a/src/content/ci/circleci.mdx b/src/content/ci/circleci.mdx
@@ -269,9 +269,9 @@ Chromatic can be run on monorepos that have multiple subprojects. Each subprojec
 #### Prerequisites
 
 1. Ensure that you're in the correct working directory for the subproject.
-2. Have `build-storybook` npm script in the subproject's `package.json` file OR explicitly name the script using the `buildScriptName` parameter and make sure the script is listed in the subproject's `package.json` file.
+2. Have `build-storybook` npm script in the subproject's `package.json` file OR explicitly name the script using the `--build-script-name` CLI flag and make sure the script is listed in the subproject's `package.json` file.
 
-If you've already built your Storybook in a separate CI step, you can alternatively point the action at the build output using the `storybookBuildDir` parameter.
+If you've already built your Storybook in a separate CI step, you can adjust your workflow to include the `--storybook-build-dir` CLI flag to point to the build output directory.
 
 ```yml title=".circleci/config.yml"
 # Other required configuration

diff --git a/src/content/ci/custom-ci-provider.mdx b/src/content/ci/custom-ci-provider.mdx
@@ -2,7 +2,7 @@
 layout: "../../layouts/Layout.astro"
 title: Automate Chromatic with your custom CI provider
 description: Learn how to configure Chromatic with a custom provider
-sidebar: { order: 8, label: Other CI providers }
+sidebar: { order: 9, label: Other CI providers }
 ---
 
 import IntegrationSnippets from "../../components/IntegrationSnippets.astro";
@@ -119,9 +119,9 @@ Chromatic can be run on monorepos that have multiple subprojects. Each subprojec
 #### Prerequisites
 
 1. Ensure that you're in the correct working directory for the subproject.
-2. Have `build-storybook` npm script in the subproject's `package.json` file OR explicitly name the script using the `buildScriptName` parameter and make sure the script is listed in the subproject's `package.json` file.
+2. Have `build-storybook` npm script in the subproject's `package.json` file OR explicitly name the script using the `--build-script-name` CLI flag and make sure the script is listed in the subproject's `package.json` file.
 
-If you've already built your Storybook in a separate CI step, you can alternatively point the action at the build output using the `storybookBuildDir` parameter.
+If you've already built your Storybook in a separate CI step, you can adjust your workflow to include the `--storybook-build-dir` CLI flag to point to the build output directory.
 
 ```yml title="your-workflow.yml"
 # 👇 Runs Chromatic sequentially for each monorepo subproject.

diff --git a/src/content/ci/gitlab.mdx b/src/content/ci/gitlab.mdx
@@ -220,9 +220,9 @@ Chromatic can be run on monorepos that have multiple subprojects. Each subprojec
 #### Prerequisites
 
 1. Ensure that you're in the correct working directory for the subproject.
-2. Have `build-storybook` npm script in the subproject's `package.json` file OR explicitly name the script using the `buildScriptName` parameter and make sure the script is listed in the subproject's `package.json` file.
+2. Have `build-storybook` npm script in the subproject's `package.json` file OR explicitly name the script using the `--build-script-name` CLI flag and make sure the script is listed in the subproject's `package.json` file.
 
-If you've already built your Storybook in a separate CI step, you can alternatively point the action at the build output using the `storybookBuildDir` parameter.
+If you've already built your Storybook in a separate CI step, you can adjust your workflow to include the `--storybook-build-dir` CLI flag to point to the build output directory.
 
 ```yml title=".gitlab-ci.yml"
 # .gitlab-ci.yml

diff --git a/src/content/ci/jenkins.mdx b/src/content/ci/jenkins.mdx
@@ -208,9 +208,9 @@ Chromatic can be run on monorepos that have multiple subprojects. Each subprojec
 #### Prerequisites
 
 1. Ensure that you're in the correct working directory for the subproject.
-2. Have `build-storybook` npm script in the subproject's `package.json` file OR explicitly name the script using the `buildScriptName` parameter and make sure the script is listed in the subproject's `package.json` file.
+2. Have `build-storybook` npm script in the subproject's `package.json` file OR explicitly name the script using the using the `--build-script-name` CLI flag and make sure the script is listed in the subproject's `package.json` file.
 
-If you've already built your Storybook in a separate CI step, you can alternatively point the action at the build output using the `storybookBuildDir` parameter.
+If you've already built your Storybook in a separate CI step, you can adjust your workflow to include the `--storybook-build-dir` CLI flag to point to the build output directory.
 
 ```groovy title="JenkinsFile"
 pipeline {