ci.dispatch¶
Start a point on the forge by hand and follow it to its verdict.
The gate and the nightly carry a dispatch entry. A dispatched
gate pays the full gate on ref, since the check verb narrows on
a pull request alone, and its stamp writes a full row for the
tree it proved; the nightly's run waits for nobody, and this verb
starts the same run now, so a failure only the nightly meets (a
floor Python, a release's verification) is reproduced on demand.
The run followed is the dispatch's own: the one the forge names,
or the one dispatched run of ref, at the commit origin names for
it, that appeared after the dispatch. Two such runs refuse, naming
both. Exits green 0, red 13 with the red jobs named, a run that
never registered or a wait that runs out 14, a forge unreachable
for five polls in a row 15, and, with --no-follow, 18 while
the run moves. The merge point runs on a push alone, and the
release wave is the merge point's to dispatch.
fm ci.dispatch [--point=VALUE] [--ref=VALUE] [--no-follow] [--interval=INT] [--timeout=INT] [--only=VALUE]
| Parameter | Type | Default | Description |
|---|---|---|---|
--point=VALUE |
"nightly" |
the point to start: gate, nightly, or one a package contributes | |
--ref=VALUE |
"main" |
the branch or tag the run checks out | |
--follow |
flag | true |
wait for the run's verdict |
--interval=INT |
int | 15 |
poll seconds |
--timeout=INT |
int | 1800 |
deadline seconds for the verdict |
--only=VALUE |
"" |
the scheduled tasks the run takes, comma-separated, for the nightly: ci.e2e rehearses the loop alone; empty runs everything |