Skip to content

ci: rebuild Docker images whose floating tags lag the latest release - #2726

Open
zaccesss wants to merge 1 commit into
php:mainfrom
zaccesss:ci/repoint-stale-floating-tags
Open

zaccesss wants to merge 1 commit into
php:mainfrom
zaccesss:ci/repoint-stale-floating-tags

Conversation

@zaccesss

Copy link
Copy Markdown

Follow-up to #2710, cc @dunglas @AlliBalliBaba.

The nightly run skips a variant when its base images match the fingerprint on the versioned builder tag. When the scheduled run on 11 October went out while v1.13.1 was still a draft, it rebuilt v1.13.0 and pushed the floating major tags back to it. After the release was published, the Debian bases had changed, so those variants were rebuilt and their floating tags moved forward. The Alpine bases had not, so Alpine was skipped and the floating Alpine tags are still on v1.13.0.

Current state on Docker Hub:

Tag org.opencontainers.image.version Base fingerprint
1.13.1-builder-php8.4-alpine v1.13.1 9fb1ee49dd1c
1-builder-php8.4-alpine v1.13.0 9fb1ee49dd1c
1-builder-php8.4-trixie v1.13.1 b5ec56f7d93f

This PR adds one more condition before skipping a variant: the floating major builder tag must already carry the latest release version. On a normal night nothing changes, because the floating tag is already on the latest release. After a release like this one, the stale variants get rebuilt and their floating tags repointed.

Checked with bash -n and shellcheck. If you would rather not change the workflow, feel free to close this; a manual run of the Docker workflow on v1.13.1 would fix the current tags.

The nightly run skipped a variant whenever its base images matched the versioned builder tag. If a scheduled run went out while a release was still a draft, the floating major tags were pushed back to the previous release. Nothing moved them forward again until a base image changed, which left 1-php8.4-alpine on 1.13.0 after 1.13.1 was published.

Also require the floating major builder tag to carry the latest release version before skipping a variant.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant