2 commits

Author	SHA1	Message	Date
mateo-berri	bb60422e7d	compat-matrix: replace publisher.py + resolver.py with a bash run_daily.sh ... The previous iteration of this PR ported the populator to a Python module (`publisher.py`) with 8 unit-tested pure helpers for branch naming and PR-body rendering. After the docker code came out, the GitHub App auth came out, and the worktree-vs-tempdir decision was made, what was left was: 'git fetch + git checkout + uv sync + start a subprocess + run pytest + clone docs + git commit + gh pr create'. That's a bash script. This commit replaces 800 lines of Python (publisher.py + resolver.py + their unit tests) with a 297-line run_daily.sh and a 48-line build_matrix.py whose only job is to be importable Python that can call into the matrix_builder we already have. Net deletion: -822 lines. Removed ------- * tests/claude_code/publisher.py — the full Python orchestrator. Every code path it had is now in run_daily.sh. * tests/claude_code/resolver.py — the GitHub Releases v*-stable resolver. Replaced by ~10 lines of jq inside run_daily.sh. * tests/claude_code/_publisher_unit_tests/ — both test files. The pure helpers they covered (commit message, file allowlist, branch name, PR title/body) only existed because publisher.py was Python. The bash equivalents are short heredoc strings. Added ----- * tests/claude_code/cron_vm/run_daily.sh — the actual cron job, structured as numbered phases (resolve / worktree / proxy / pytest / build / publish) so journalctl output is readable. * tests/claude_code/cron_vm/build_matrix.py — a 48-line CLI that calls the existing matrix_builder.build_from_paths. Kept in Python because the builder itself is Python and well-tested. Modified -------- * tests/claude_code/cron_vm/litellm-compat-matrix.service — ExecStart now invokes run_daily.sh instead of 'python -m tests.claude_code.publisher'. * tests/claude_code/cron_vm/README.md — updated layout table, file roles, and operating commands to match. Why this is the right shape --------------------------- * The failure mode at 06:00 UTC is 'read journalctl, see the literal failing command with its + prefix, copy-paste it into a shell to reproduce'. Bash makes that immediate; Python's subprocess.run output looks similar but the surrounding orchestration is harder to step through interactively. * Every operation the script does is already a shell command (git, uv, gh, jq, curl, pytest). The Python wrapper was translating between argv arrays and back. * The two pieces that genuinely benefit from being in a typed language are matrix_builder (already Python) and the resolver's semver sort (now done in jq, with the version_key tuple sort inline). 'Already Python' wins, 'tiny jq pipeline' wins. What's preserved ---------------- * Idempotency: same (litellm, claude, UTC date) -> same branch -> same PR. force-with-lease push, gh-pr-create no-op-on-exists. * Byte-identical-JSON early return (git diff --cached --quiet). * Per-feature status table in the PR body (jq pipeline mirroring the Python pr_body_for_matrix logic). * Persistent worktree approach so disk doesn't grow unboundedly. * Proxy bound to :4100 to avoid colliding with a developer's :4000. * SKIP_PUBLISH=1 and PYTEST_K=... operator escape hatches.	2026-05-06 23:27:14 +00:00
mateo-berri	449a44dba3	compat-matrix: run from a GCP VM via systemd; drop docker + GHA ... The daily compat-matrix runs from the dedicated GCP VM `litellm-compatibility-matrix-populator` rather than from a GitHub Actions runner. The VM has no docker daemon, has `gh` already authenticated against an account with `pull-requests: write` on `BerriAI/litellm-docs`, and runs a long-lived litellm checkout we can reuse across runs. That makes Docker, the GitHub App auth flow, and the GHA workflow itself dead code. Removed ------- * `.github/workflows/claude_code_compat_matrix.yml` — no longer triggers anything; the systemd timer in this PR owns the daily fire. * `docker_image_for_tag` + `DOCKER_IMAGE_BASE` constants and the two unit tests that covered them. * `_start_proxy(image, port)` / `_stop_proxy(container_id)` / `docker run` flow, replaced by direct `uv run litellm` subprocess management with a sigterm-the-process-group teardown. * `--skip-proxy` CLI flag (was only useful when the GHA workflow split docker-bringup from publish into separate jobs). * `docs_token` parameter and `DOCS_REPO_TOKEN` env var; `gh` on the VM is already authenticated, so we don't pass an explicit token through the publisher. Added ----- * Persistent worktree flow in `publisher.py`. First run clones `BerriAI/litellm` into `~/litellm-cron-worktree/`; subsequent runs do `git fetch --tags && git checkout --force <stable-tag> && uv sync --frozen`. Disk footprint is bounded because uv sync removes packages no longer pinned and `git clean -fdx -e .venv` wipes per-run cruft while keeping the venv around. * `tests/claude_code/cron_vm/` containing systemd units and a setup README: - `litellm-compat-matrix.service` (`Type=oneshot`, runs as the `mateo` user, sources `/etc/litellm-compat-matrix.env` for provider creds, hardened with `NoNewPrivileges` / `ProtectSystem=strict` / `PrivateTmp`); - `litellm-compat-matrix.timer` (`OnCalendar=*-*-* 06:00:00 UTC`, `Persistent=true` so a missed run fires when the VM is back up, `RandomizedDelaySec=10min`); - `.env.example` documenting the provider-credential surface; - `README.md` covering one-time install, daily operation, `journalctl` debugging, and the gotchas (proxy port `4100` to avoid colliding with a developer's `:4000`, `gh` token rotation, what to do after a Claude Code CLI upgrade). Operator notes -------------- * The proxy now binds `:4100` by default so a developer SSH'd into the VM with their own `:4000` proxy isn't preempted by the cron. * The Claude Code CLI is exercised as-is from the system install; the populator does NOT `npm install` it. Operators upgrade the CLI by running `npm install -g @anthropic-ai/claude-code@latest` out of band, typically after watching a `--skip-publish` run to verify the matrix doesn't suddenly turn red. * 20 publisher unit tests pass (`pytest tests/claude_code/_publisher_unit_tests/`). * End-to-end validation on the VM happens after this PR lands as follow-up commits on the same branch — the systemd unit is `Type=oneshot` so a manual `systemctl start` reproduces the cron.	2026-05-06 23:27:14 +00:00