stado product cargo
Invocation
stado product cargo [OPTIONS] <operation> [ARGUMENTS]...Purpose
Run Cargo against canonical checkouts or declared release-worker source inputs
Required inputs and options
| Input or option | Contract |
|---|---|
<operation> | build, check, test, run, metadata or stage on any tree, or any Cargo subcommand a quality gate of the built tree's .wisent-release.json runs (clippy; not fmt, which compiles nothing): read under --revision from that committed revision. stage: a locked release build of the forwarded --bin targets, each binary placed at $WISENT_OUTPUT_DIR/<name> for a release manifest to stage [ARGUMENTS]... Arguments passed to the real compiler after the operation |
--catalog <catalog> | Independent authoritative catalog path |
--manifest-path <manifest-path> | Canonical Cargo.toml; defaults to the current directory |
--revision <revision> | Build this committed revision of the manifest's repository instead of its working tree: the commit is exported once into the checkout's build area (~/.stado/products/builds/<checkout below home>/stado-build/<commit>/) and read and built there with the same locked flags and compiler cache, so another session's uncommitted edit in the checkout is not read; a commit the checkout does not hold is refused |
--workspace <workspace> | The workspace of canonical checkouts this operation reads and builds from; default WISENT_WORKSPACE, else ~/Documents/CodingProjects/Wisent |
--all | Read retained Cargo receipts across canonical workspace checkouts; results only |
--json | Print retained source and execution evidence |
--wait | When the disk janitor has asked running work for its turn, wait for that work, run the janitor's pass and then build, instead of being refused before anything is exported or built |
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
- Build this committed revision of the manifest's repository instead of its working tree: the commit is exported once into the checkout's build area (~/.stado/products/builds/<checkout below home>/stado-build/<commit>/) and read and built there with the same locked flags and compiler cache, so another session's uncommitted edit in the checkout is not read; a commit the checkout does not hold is refused
- When the disk janitor has asked running work for its turn, wait for that work, run the janitor's pass and then build, instead of being refused before anything is exported or built
- 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.