stado builds add
Invocation
stado builds add [OPTIONS] --name <NAME> --repo <REPO> --branch <BRANCH> --command <COMMAND> --artifact <ARTIFACTS> --platform <PLATFORMS>Purpose
Add a build recipe. Recipes start disabled; enable one explicitly
Required inputs and options
| Input or option | Contract |
|---|---|
--name <NAME> | Unique kebab-case recipe name |
--repo <REPO> | HTTPS clone URL of the repository to build |
--branch <BRANCH> | Branch the poller watches |
--command <COMMAND> | Single POSIX sh build command run in the checkout |
--artifact <ARTIFACTS> | Path in the checkout to upload as a build artifact (repeatable) |
--platform <PLATFORMS> | Release platform to build for, e.g. `darwin-arm64` (repeatable, at least one). Each platform gets its own build job, claimed only by a worker that is actually that platform |
--auto-declare | Declare a successful run's tag version on every registry host of that platform. Never promotes a signed release |
--interval-seconds <INTERVAL_SECONDS> | Poll cadence in seconds (default 300) [default: 300] |
--json | Emit the created recipe as JSON |
Output and state effect
It performs the operation described above and emits its operator result on standard output or standard error. Any state change is limited to the resources and records named by the purpose and options on this page.
Refusals
- Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.