mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 10:59:59 +00:00
kevinveenbirkenbachandClaude Opus 5
db66e01020
call-test-deploy-{compose,host,swarm,single-node}.yml differed only in
which mode they pinned and which artifact prefix they wrote; compose and
host already ran the identical drill. They become one call-test-deploy.yml
whose matrix rows carry the mode, so the swarm-specific steps are guarded
on it and everything else is shared.
The orchestrator loses its eight deploy jobs and the sequencing job for
three serial chunk blocks. GitHub Actions cannot generate a variable
number of jobs, so the blocks are written out and INFINITO_CI_MAX_CHUNKS
tells the budget how many exist; blocks whose slice is empty skip
themselves. chunk_gate stops the chain at the first red chunk,
resume_from_chunk re-enters after a fix instead of re-running the green
chunks, and modes collapses to a single mode choice.
apps.sh now emits matrix entries for one chunk rather than a token list
for one mode, and no longer sorts them: the discovery order is what the
chunker slices on. split_runner_apps.sh reads its runner quota from
INFINITO_CI_CONCURRENCY instead of carrying a second copy of the 20.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
19 lines
595 B
Bash
Executable File
19 lines
595 B
Bash
Executable File
#!/usr/bin/env bash
|
|
#
|
|
# Resolve the chunk's deploy matrix and write it to GITHUB_OUTPUT.
|
|
# Inputs via env (forwarded to scripts/meta/resolve/apps.sh):
|
|
# INFINITO_CI_CHUNK — chunk index to emit
|
|
# INFINITO_CI_SWEEP — sweep number
|
|
# INFINITO_WHITELIST / INFINITO_PRIORITY / INFINITO_MODES / INFINITO_TOR
|
|
set -euo pipefail
|
|
|
|
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
|
|
REPO_ROOT="$(cd "${SCRIPT_DIR}/../../.." && pwd)"
|
|
cd "${REPO_ROOT}"
|
|
|
|
matrix="$(./scripts/meta/resolve/apps.sh)"
|
|
[[ -n "$matrix" ]] || matrix='[]'
|
|
|
|
echo "apps=$matrix" >>"$GITHUB_OUTPUT"
|
|
echo "apps=$matrix"
|