6.7 app image tag wasn't created on release

[pdurbin]

The plan was for a 6.7 tag to appear at https://hub.docker.com/r/gdcc/dataverse/tags when 6.7 was released but we've hit a little snag, as discussed on Slack.

I'm looking at https://github.com/IQSS/dataverse/actions/runs/16376088170 and the "Application Image Matrix Build" job failed with Error: Could not find gdcc/base:6.7-noble-r-1 in the registry.

According to https://hub.docker.com/r/gdcc/base/tags we do have these:

• gdcc/base:6.7-noble
• gdcc/base:6.7-noble-p6.2025.3-j17

But we don't have the one we seem to need: 😢

• gdcc/base:6.7-noble-r-1

I wonder if we can force r-1 to build and then retry the "Application Image Matrix Build" job. :thinking_face: There is a "run workflow" button at https://github.com/IQSS/dataverse/actions/workflows/container_maintenance.yml with a checkbox for "Build and deploy even if no newer Java images or package updates are found."

Related:

• Fix ct image releasing #11660
• "latest" tag and revision tag (e.g. 6.7-noble-r0) were not created on Docker Hub for 6.7 app image #11661
• "latest" tag was not created on Docker Hub for 6.7 base image #11662

[poikilotherm]

It's good we don't have an "-1" image... 😉

The actual problem was, that the base image wasn't built once we released. As we had a rolling tag on the Hub, it checked that for updates. As there were none to do, it did not built the base image, thus it did not create a "r0". This made the app image job fail.

What we need is a simple additional build trigger: if we're not on a develop branch and there is no revisioned (fixed) image available, force a build. We don't need this trigger for the app image maintenance script, as the base image will be newer than any available rolling tags from the dev branch that are on the Hub already.

Fun side fact: releasing today would have had us not hit this - there was a JDK image update over the weekend.