magus v0.4.3 is out. See what's new
¶ View markdown source · ✎ Suggest an edit
1 min read

chained-run

An advisory: it explains, and blocks nothing, on several magus runs chained on one line, where the dependency graph would have run them.

What it catches

Several magus runs chained on one line, where the dependency graph would have run them.

Why

Targets compose through ctx.needs, so the last one usually pulls the rest in order and each extra invocation reloads the workspace. It ADVISES rather than refuses because two genuinely independent targets on one line are real work, and only the graph knows which case this is. The exception worth knowing: affected ci does not regenerate. Where the gate strips the workspace's default charms, its composed generate is a drift gate, so affected generate:rw comes first as its own invocation.

Seeing it

A verdict names its rule in brackets, which is how you got here:

advise [chained-run]: ...

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
guardruleschained-runadvise
Last updated (b4f68ff3)
Glossary

Workspace

The magus root directory that owns a set of projects and shared config; the unit magus operates over. See workspace.

Target

A named operation (build, test, ...) you invoke with magus run <target>; it may compose a spell's tool-native operations and depend on other targets. See targets.

Charm

An execution modifier attached with : (lint:rw) that changes how a target runs, not which one; the built-in rw flips a check-only target to mutate in place, and ci always strips it. See charms.

Affected

The set of projects touched by a change; magus affected <target> runs a target only over them. See affected.

CI

An ordinary magusfile-defined target you compose yourself with magus\needs - magus does not hardcode its stages. Magus.RunCI treats it specially only in that it strips the rw charm, it is the anchor magus affected ci keys off, and a selected scope with no project declaring it is a load error rather than a silent no-op. See targets.

Invocation

One magus process's recorded facts - the targets it finished, their outcomes, the lease it acted as, and the session it ran in when a host delivered one - kept in a repo-scoped store every worktree shares. magus session lists them; the store prunes itself by last-fact age.

Run

One target executing under one magus invocation, such as magus run test web or magus affected ci. A run keeps its captured output behind an output reference. Every magus run is a run whether or not any job asked for it; see Job for how the two relate.

Advisor

One read-only check from the advice suite: it reads the changeset through magus and writes one titled section of findings. The same advisors run as a pull request comment in CI and inside magus diff --impact locally.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.