mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 11:46:35 +00:00
kevinveenbirkenbachandClaude Opus 5
bc8e45b934
The CI deploy bootstrap hand-listed two packages and let the ubuntu-latest runner image supply the rest, so a new host-side import surfaced as a red deploy job instead of a failed install. Size [project.dependencies] to what runs outside the project image and move the deployment stack into a deploy extra, then have every install site read that instead of naming packages itself: the image build and make install-python take the deploy extra, the CI host and the mirror and instructions workflows take the base. Declare cryptography, which utils/manager/value_generator.py imports directly and which only reached the environment transitively through ansible. Drop numpy, which nothing in the repository imports. Guard the boundary with a lint test that blocks every deploy package and asserts the runner-host CLI still builds its parser. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CI Deploy Scripts
This directory holds the executable CI deploy flows under scripts/tests/deploy/ci/.
For local deploy flows, use ../local/README.md.
Entry Points
| Script | What it does | Notes |
|---|---|---|
all.sh |
Runs one app across all selected distros, serially. | Uses dedicated.sh for the per-distro deploy loop. |
dedicated.sh |
Deploys one app on one distro twice against the same stack. | Performs the full CI cleanup after the run. |