stado build submit
Invocation
stado build submit [OPTIONS] --source <SOURCE> --version <VERSION>Purpose
Build one committed source on every platform its manifest declares. Snapshots the committed tree, publishes it as an immutable source object and queues one build job per platform on a live fleet builder. It ends when the jobs are queued; `stado build status` follows them. Nothing is signed, published or promoted: that is `stado release submit --build`, which consumes only a build that has passed. Repeating the command for the same source resumes the same build and re-queues only the platforms whose job failed or was cancelled.
Required inputs and options
| Input or option | Contract |
|---|---|
--source <SOURCE> | The product checkout to build |
--commit <COMMIT> | Read this full Git commit without changing or requiring a clean checkout |
--version <VERSION> | The version that commit declares in its version source |
--platform <PLATFORMS> | Build only this declared platform; repeat for several. The build and any release of it then cover exactly these platforms. Without it every platform the manifest declares is built |
--json | Command option; required or optional as shown in the invocation. |
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.