ci.e2e¶
Exercise the CI and release story on a local environment, by scenario.
--env names the environment the pass runs on, e2e by
default: one that does not exist is brought up in host mode
with one runner, --fresh removes it and brings it up
again, so a fresh pass is a new forge, and --purge-cache
removes the rig's shared caches first. The docker-mode
environment dev is the compose rig, addressed as before.
Each variable an extension of the loop's set declares with a
directory of its own is placed inside the environment, so what a
release writes there goes with the environment's forge.
--scenario names what the pass proves: scenario names, set
names, or both, comma-separated. The sets are develop
(birth, the verified skip, the members, the scoped leg), the
default, release (develop and the release act), points
(the nightly, the dispatched gate, the contributed point),
extension (birth and the members) and all; a scenario's
needs run first, once. --extension tests one extension in
isolation, extension the default set: the birth lists that
extension and what it requires instead of the loop's stack, and
the members are the loop's whose sets hold an extension its steps
name. birth builds
this checkout's workshop, its dependencies and the extensions a
birth lists into a local index, births or resumes the loop's
workspace through fm new.project from that index (so an
extension the birth lists needs no release), with its
repository, protection and setup pull request, provisions the
secrets, wires the workspace to the dev wheels in the forge's
registry, and follows the pushed head's runs to their verdicts
on the real runner. Re-running is the recovery procedure at every
step. The pass ends with a table, each scenario's time and
runs, and records the same rows on the local loop series.
--fresh starts over from nothing: the loop's repository on
the dev forge, its releases in the forge's registry, and the
local workspace go, then the pass births everything anew. It
refuses while the workspace holds commits the forge has not
seen. --from-main moves a checkout standing on main or a
reserved workflow/ branch, where a build would be the release
train, to a scratch branch at the same commit for the pass and
back afterwards; the nightly's checkout is one.
fm ci.e2e [--forge=VALUE] [--fresh] [--scenario=VALUE] [--env=VALUE] [--purge-cache] [--extension=VALUE] [--from-main]
| Parameter | Type | Default | Description |
|---|---|---|---|
--forge=VALUE |
"gitea" |
||
--fresh |
flag | false |
|
--scenario=VALUE |
"" |
||
--env=VALUE |
"e2e" |
||
--purge-cache |
flag | false |
|
--extension=VALUE |
"" |
||
--from-main |
flag | false |