Skip to content

Jenkinsfile: build with BuildKit - #6

Merged
skudin13 merged 1 commit into
mainfrom
PTEUDO-4980-jenkins-buildkit
Oct 30, 2026
Merged

skudin13 merged 1 commit into
mainfrom
PTEUDO-4980-jenkins-buildkit

Conversation

@skudin13

Copy link
Copy Markdown
Collaborator

Overview

Build the image with BuildKit in the Jenkinsfile.

What this PR does / why we need it

After #5 the Dockerfile contains the upstream image check RUN --mount=type=bind,... verify-image.sh. --mount needs BuildKit, and the Jenkins agents (Docker 20.10) use the legacy builder by default, so the main build failed with the --mount option requires BuildKit.

This sets DOCKER_BUILDKIT=1 for the docker build step. The Dockerfile stays identical to upstream, so future upstream syncs do not conflict.

How tested

Special notes for your reviewer

  • Jenkinsfile only, no image content change.

The Dockerfile now has an upstream image check that uses RUN --mount,
which needs BuildKit. The Jenkins Docker 20.10 agents ship BuildKit but
keep it off by default, so main build flant#9 failed with
'the --mount option requires BuildKit'. Set DOCKER_BUILDKIT=1 for the
build step and keep the Dockerfile identical to upstream.

PTEUDO-4980

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@skudin13 skudin13 added the enhancement New feature or request label Oct 30, 2026
@skudin13
skudin13 merged commit 929b4d5 into main Oct 30, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant