chained-run
A deny rule by default: it refuses magus runs sequenced with && or ;, which a pipe of the same stages runs ordered and fail-fast, and names what to run instead.
What it catches
Magus runs sequenced with && or ;, which a pipe of the same stages runs ordered and fail-fast.
Why
A pipe of magus runs keeps what the chain was for: stages whose projects overlap run in order, a failed stage stops the ones after it, and the last stage exits with the first failure (MGS3030), so no set -o pipefail is needed. It differs from && in one way, which the deny states: a stage on disjoint projects runs alongside the others and finishes even after an upstream stage fails. The pipeline still exits red. The same target chained over several project sets is served the pipe too, which keeps the order the chain chose; the deny names the one call for when order does not matter. It advises instead, and says why, wherever the pipe would do something else. That covers ||, a redirect or any other command on the line, and a later affected stage, which reads its projects from the diff before the upstream's writes land: affected generate:rw stays its own call ahead of affected ci. It also covers a later run naming no projects, which would inherit the upstream's; a stage that reads stdin, takes no locks, or writes -o output upstream; stages on different binaries or roots; a stage after go-build or build in magus's own checkout, since every stage starts at once and would run the ./magus being replaced; and Windows, where no pipe proves its upstream.
Default and override
By default this rule takes the decision deny. A workspace sets it by name, in its root
magusfile, to deny, advise or off:
magus\guard.builtins({"chained-run": "advise"})
A loosening takes effect once it is committed; a tightening applies at once.
Seeing it
A verdict names its rule in brackets, which is how you got here:
deny [chained-run]: ...
A workspace that sets this rule to advise sees advise [chained-run]: ... instead.
magus describe rule chained-run prints the same entry at a terminal, and
magus describe rules lists every rule this workspace enforces.
See also
- All rules - what this workspace enforces, deny first
- The guard - how a verdict is reached and wired
- Setting a built-in rule - how a workspace changes this default