A nightly build an hour after docker system prune -af first rebuilt
its image (233 s on vm4006) and ran into the build timeout. The cleanup
now keeps images labelled org.werkator.build-inputs-sha256 on six nights
and takes them in the night to Sunday, so the base image is at most a
week old. A replaced build image loses its tag but keeps the label, so docker image prune -f follows.
A nightly build an hour after `docker system prune -af` first rebuilt
its image (233 s on vm4006) and ran into the build timeout. The cleanup
now keeps images labelled org.werkator.build-inputs-sha256 on six nights
and takes them in the night to Sunday, so the base image is at most a
week old. A replaced build image loses its tag but keeps the label, so
`docker image prune -f` follows.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A nightly build an hour after `docker system prune -af` first rebuilt
its image (233 s on vm4006) and ran into the build timeout. The cleanup
now keeps images labelled org.werkator.build-inputs-sha256 on six nights
and takes them in the night to Sunday, so the base image is at most a
week old. A replaced build image loses its tag but keeps the label, so
`docker image prune -f` follows.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A nightly build an hour after
docker system prune -affirst rebuiltits image (233 s on vm4006) and ran into the build timeout. The cleanup
now keeps images labelled org.werkator.build-inputs-sha256 on six nights
and takes them in the night to Sunday, so the base image is at most a
week old. A replaced build image loses its tag but keeps the label, so
docker image prune -ffollows.Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com