Files
computer-playbook/scripts/image
kevinveenbirkenbachandClaude Opus 5 ef45d69dc3 perf(image): build the collections into a layer the source cannot invalidate
COPY . preceded every expensive RUN, so each commit rebuilt the whole
chain and ansible-galaxy ran on every build of every distro. The
collection install now sits in its own layer fed only by default.env,
scripts/install, the dev-python shell scripts, requirements/ and the
three files the version check imports. Everything that needs the full
tree, the project's own distro package included, stays behind COPY ..

Measured on a role-only change: the collection layer stays CACHED and
the build drops to 3m10s against a CI baseline of 855-899s. An
unchanged rebuild is 15 cached layers in 1.5s.

The gha cache imported and exported nothing in a plain run step, so the
export moves to the registry the job already authenticates against.
ignore-error keeps a cache write failure from taking the build with it,
which it otherwise does: proven against an unreachable registry, where
the build fails hard without it and exits 0 with it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-16 20:54:49 +02:00
..
2026-08-18 03:22:05 +02:00
…

Image Scripts

This directory contains scripts related to the image lifecycle used by the project.

  • 🏗️ Build container images for local and CI workflows
  • 📦 Publish, retag, and maintain image artifacts in registries
  • 🔧 Keep image-focused automation grouped in one place

The scope of this folder is image handling. Workflow orchestration, metadata resolution, and generic waiting logic should live in other script directories.