Run on this computer

Build, test and package locally — no server or SSH needed.

Contents

A workflow doesn't have to deploy anywhere. Set Runs on to This computer and CID runs its steps right here, in the project's local folder. That's ideal for building installers, running tests, or packaging a release.

Choose a shell

Shell	Variables	How errors work
Command Prompt (default)	`%NAME%`	A one-line step runs exactly as typed. In a multi-line step every line runs; use `&&` or `if errorlevel` to stop early.
PowerShell	`$env:NAME`	Stops at the first error, and a failing program's exit code fails the step.
Git Bash	`$NAME`	Stops at the first failing command (`set -eo pipefail`). Only offered if Git for Windows is installed.

On macOS and Linux, steps always run with Bash (stopping at the first failing command), and variables look like $NAME. On macOS and Linux, CID uses the same PATH as your terminal, so tools installed with Homebrew or nvm are found, even when CID is opened from the Dock or the app menu. It reads the PATH once when it starts, so restart CID after installing a tool or changing your default nvm version.

What steps can rely on

Steps start in the project's local folder, or in the step's own working folder if you set one — see Steps.
Your project's variables and secrets are set as environment variables.
CID_ARTIFACTS_DIR points at a folder where anything you save is kept with the run — see Artifacts.
Nothing is uploaded anywhere: no files are synced, and no SSH key or server is needed.

Build release (PowerShell)

$ npm ci

$ npm run build

$ Copy-Item dist\*.zip $env:CID_ARTIFACTS_DIR

Cancel run stops the whole process tree a step started — including things like npm run … children — not just the shell.

Run your first workflow Steps

$ loading▍

Run on this computer

Choose a shell

What steps can rely on

Ask Pumpkin

Hi, I'm Pumpkin.

Run on this computer

Choose a shell

What steps can rely on