mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 10:59:59 +00:00
kevinveenbirkenbachandClaude Opus 5
623ecc0248
Which of the two sources is faster is not a constant. galaxy.ansible.com degraded from 207s to 687s over one day and then served 502s outright, while the pinned git fallback carried the same install in 31s; a week later the order may be the other way round. The daily job times both and swaps the default only when the preferred one's median reaches three times the other's over twelve samples. A failed install is recorded as None and ranks worse than any duration, so an outage counts instead of dropping out of the statistic. Below a full window nothing changes, which keeps a single bad day from flipping the default. History lives in an artifact rather than the Actions cache: a schedule run resolves to the default branch and has read-only cache access there, so it could not carry the window forward. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
14 lines
306 B
Bash
Executable File
14 lines
306 B
Bash
Executable File
#!/usr/bin/env bash
|
|
set -euo pipefail
|
|
|
|
SCRIPT_DIR="$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" && pwd)"
|
|
REPO_ROOT="$(cd -- "${SCRIPT_DIR}/../../.." && pwd)"
|
|
|
|
cd "${REPO_ROOT}"
|
|
make dotenv >/dev/null
|
|
set -a
|
|
# shellcheck disable=SC1091
|
|
. .env
|
|
set +a
|
|
python3 -m cli.contributing.update.collection_source "$@"
|