ci: clean up after image builds and demo wipes
All checks were successful
PR Checks / bot-tests (pull_request) Successful in 53s
PR Checks / client-build (pull_request) Successful in 2m19s
PR Checks / server-tests (pull_request) Successful in 6m19s

The build job runs docker on the runner host's daemon, so every run left
four tagged images behind for good. Remove this run's tags once they are
pushed and cap BuildKit's cache at 5 GB, always, never failing the job.

The demo wipe pulls every two hours; drop the dangling image each pull
replaces. The uom-deploy-runner deploy job is deliberately untouched.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
This commit is contained in:
2026-11-02 11:20:47 -06:00
parent 27f7fe5d85
commit ebb8f870bb
2 changed files with 24 additions and 0 deletions

View File

@@ -110,6 +110,14 @@ jobs:
docker run --rm --network rg-demo_default -v "$DEMO_DIR:/demo" \
-e SITE_URL=http://app:3000 "$NODE_IMAGE" node /demo/rig.mjs smoke
- name: Remove the images this wipe replaced
# Each pull that finds a newer `latest` leaves the old image untagged on
# the demo host, every two hours. Untagged images are never used again, so
# drop them. Dangling images only: nothing tagged and nothing a container
# is using is touched.
if: always()
run: docker image prune -f || true
- name: Report the rig restore
if: steps.rig.outcome == 'failure'
run: |