0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-10 12:47:04 +00:00

Files

T

kevinveenbirkenbach 8600f1d9aa test(ci-trigger): pin the workspace suite rule

The rule lived only in suite_passed's body, and it inverts easily on a
casual read: ask for the suite again when it failed. Under that reading
the retrigger aliases would drop the suite in their most common case,
because they force-cancel the source run before reading it, so a shard
that was still running comes back cancelled rather than red.

Only an all-green suite is retired. Failed, cancelled, skipped, timed
out, still running and never dispatched all keep it on the retrigger,
and each of those now has a test. The two docstrings enumerate them, and
so does the i8ciall description, which is where an operator reads it.

2026-09-03 17:37:33 +02:00

status

refactor(ci): move the git and gh plumbing out of runs.py

2026-08-16 03:38:47 +02:00

trigger

fix(ci-trigger): resume where the last run left off

2026-09-03 13:38:07 +02:00

__init__.py

…

gh.py

fix(ci): make the failed-run retrigger reach its dispatch

2026-08-18 05:21:52 +02:00

README.md

…

runs.py

test(ci-trigger): pin the workspace suite rule

2026-09-03 17:37:33 +02:00

selections.py

fix(ci-trigger): resume where the last run left off

2026-09-03 13:38:07 +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.