The runner keeps no copy of the images it builds, and trims week-old build cache #51
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/runner-cleanup"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #44.
The runner's Docker held about 100 GB on 2026-10-30. 88 GB of it was 64 local
sports-breaker:<sha>tags: publish tagged, pushed and kept every image. Since #49 a push adds about 2 MB, but each week's dependency refresh (DEPS_REFRESH) builds a new set of dependency layers, about 1.5 GB, and the old tags kept every past week's set. Left alone, that comes to about 80 GB a year.Changes
publish-image: once the push is done, the job removes:
The step runs after a failure too.
ci service lane: removes its untagged image after the e2e. It doesn't use
-f, so an image another build has since tagged stays.What to expect
until=168hreaches them.The next build's cache hits come from the build cache, not from the removed tags, so build times shouldn't change. The first develop run will confirm it.
Also: timeouts for a hung lane (
a1075ec). Run 285's pytest lane sat 25 minutes on idle xdist workers, with no browser or server under them.make testnow passes--timeout=120.pytest-timeoutis already a test dependency, and the slowest test takes about 13 s. A hung test now fails with its stack, which shows which test it was.🤖 Generated with Claude Code