tree 9a00fa6f64850c8607975bd8e7279d257c3c6ac6
parent 731d00ae802712305d2a01ea4a7bbc74227b2f0d
author Leopold Schabel <leo@nexantic.com> 1580763107 +0100
committer Leopold Schabel <leo@nexantic.com> 1580763107 +0100

Manually invalidate image cache in CI

Our objective is to ensure that the build always uses the latest
Dockerfile for a given build, while minimizing rebuilds.

A counter is explicit and can be used to intentionally invalidate
the image cache, even if the the file's content did not change.

The caching performed by `podman build` is not very clever -
it's not shared between repositories, and is easily invalidated
by successive builds with different versions of the Dockerfile.

Garbage collection is not trivial, since there may be multiple
in-flight revisions with different counters.

Ref T506

Fixes T616

Test Plan: CI ;)

Bug: T616, T506

X-Origin-Diff: phab/D373
GitOrigin-RevId: 5bfb8cd8b98175d645c904aee8e45402d0c049c7