0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-08 11:46:35 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 4.8 68c0ffa84e feat(ci-trigger): add --strict to retrigger only hard failures, plus i8cifo/i8pufo

The --failed selection treats anything not green (cancelled, timed-out, still-running) as a failure, so retriggering a partially-running or aborted run re-fires jobs that never actually failed. Add --failed --strict to select only roles with a hard failure conclusion, excluding cancelled/aborted and running. New aliases i8cifo (strict base, mirrors i8cifail) and i8pufo (sign-push then strict retrigger, mirrors i8pufail); i8pufail is unchanged. Verified against a live run: --failed matched 48 roles (8 failed + 40 still-running), --strict matched exactly the 8 hard failures.

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

2026-07-25 12:44:03 +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

feat(ci-trigger): add --strict to retrigger only hard failures, plus i8cifo/i8pufo

2026-07-25 12:44:03 +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

feat(ci-trigger): add --strict to retrigger only hard failures, plus i8cifo/i8pufo

2026-07-25 12:44:03 +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.