CLI reference / build / newest

stado build newest

Invocation

stado build newest [OPTIONS]

Purpose

Build every product in this workspace from the commit it stands on, and say what failed. Nothing is released. The same reading of the workspace as `stado release newest` — every product checkout, the commit it is on, the version that commit declares — followed by one build per product. `--plan` reads without queueing; `--wait` follows every build to its end and exits nonzero naming each product whose build failed.

Required inputs and options

Input or optionContract
--root <ROOT>The directory holding the product checkouts. Defaults to the parent of the checkout this command is run in
--product <PRODUCTS>Build only these products; repeat for several. The default is every product the workspace holds
--queuedBuild only the products with handed-off work no build has taken yet (`stado release changes list` state `queued`). This is the one batch: agents hand work off and compile nothing, and Oko's control pass runs `stado build newest --queued` over the workspace once every open task and defect carries its repair, then judges the result
--planRead what would be built and why the rest is skipped, without queueing anything
--waitFollow every queued build to its end on the local store's change watch, and exit nonzero naming each product whose build failed
--jsonCommand 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.