0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-12 21:56:21 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 5 ce2db79ee5 fix(ci-trigger): name the inputs a retrigger actually reproduces

CONFIG_INPUTS lost modes, sequencing and mode_fail_fast when the deploy
modes collapsed into one chunked sweep, but two mirrors of it did not
follow.

The --run help text enumerates what a retrigger carries over, so it was
telling the operator about three inputs the dispatch no longer has. The
job-log fixture described a run recording mode_fail_fast, a state the
dispatch can no longer produce, which left the log half of
config_from_run asserting on an input nobody writes.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-15 06:26:44 +02:00

status

fix(ci): discover host-mode deploy jobs in the failed-run trigger/status

2026-07-20 12:48:56 +02:00

trigger

fix(ci-trigger): name the inputs a retrigger actually reproduces

2026-08-15 06:26:44 +02:00

__init__.py

feat(cli): add deploy ci status + trigger commands

2026-06-25 05:43:30 +02:00

README.md

feat(cli): add deploy ci status + trigger commands

2026-06-25 05:43:30 +02:00

runs.py

fix(ci): resolve deploy job titles through the display-name codec

2026-08-15 06:09:05 +02:00

README.md

CI Deploy Runs 🚦

Inspect and trigger the compose and swarm deploy-test runs for the branch you are on. status summarises each role's per-mode result (docker, swarm, and an aggregated all) from the last run; trigger dispatches a fresh manual run for all roles, only the ones that failed last time, or an explicit list.