This issue has been created
There are 2 updates.
 
 
XWiki Docker images / cid:jira-generated-image-avatar-ce046ffe-c390-478a-83ee-b5c8e6dc589f XDOCKER-422 Open

Add a CI job that actually builds the Docker images

 
View issue   ·   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-08b0e7a7-f5fc-4e7c-ba8e-d05b626c3292 Vincent Massol created this issue on 29/Jul/26 13:07
 
Summary: Add a CI job that actually builds the Docker images
Issue Type: cid:jira-generated-image-avatar-ce046ffe-c390-478a-83ee-b5c8e6dc589f Improvement
Assignee: Unassigned
Created: 29/Jul/26 13:07
Priority: cid:jira-generated-image-static-major-3db6a6dd-c980-4f2c-a2b0-8accbd223544 Major
Reporter: Vincent Massol
Description:

Problem

Nothing in this repository ever builds the Docker image. The only CI workflow, Gradlew Check, runs
./gradlew and fails if the generated directories differ from the template — it verifies that the
generated files are up to date, never that they produce a working image.

As a result a Dockerfile can be broken on master for weeks and we only find out when the Docker
Official Images pull request is opened, which is the worst possible moment: the release has already been
announced and the fix has to go through a second round trip with the Docker Official Images
maintainers.

XDOCKER-421 is exactly that: ARG TARGETARCH was only populated by BuildKit, so the image failed to
build under the classic builder that the Docker Official Images infrastructure uses. The problem sat on
master for nine days and surfaced only in the 18.6.0 update pull request.

Proposal

Add a CI workflow that actually builds the generated {{Dockerfile}}s and checks the resulting images,
using the same classic builder that the Docker Official Images infrastructure uses, so that this class
of breakage is caught on the pull request instead of at release time.

 
 

2 updates

 
cid:jira-generated-image-avatar-08b0e7a7-f5fc-4e7c-ba8e-d05b626c3292 Changes by Vincent Massol on 29/Jul/26 13:08
 
Description: h2. Problem
Nothing in this repository ever builds the Docker image. The only CI workflow, {{Gradlew Check}}, runs
{{./gradlew}} and fails if the generated directories differ from the template — it verifies that the
generated files are up to date, never that they produce a working image.

As a result a {{Dockerfile}} can be broken on {{master}} for weeks and we only find out when the Docker
Official Images pull request is opened, which is the worst possible moment: the release has already been
announced and the fix has to go through a second round trip with the Docker Official Images
maintainers.

XDOCKER
\ -421 is exactly that: {{ARG TARGETARCH}} was only populated by BuildKit, so the image failed to
build under the classic builder that the Docker Official Images infrastructure uses. The problem sat on
{{master}} for nine days and surfaced only in the 18.6.0 update pull request.

h2. Proposal
Add a CI workflow that actually builds the generated {{Dockerfile}}s and checks the resulting images,
using the same classic builder that the Docker Official Images infrastructure uses, so that this class
of breakage is caught on the pull request instead of at release time.

Assignee: Vincent Massol