release builder-images 9b27b99b0d #57

Merged
pipeline-bot merged 4 commits from _promote/9b27b99b0db3 into main 2026-07-29 03:55:30 +00:00
Collaborator
No description provided.
Vendored-copy sync. This script ships in two repos and its header requires the
copies stay identical; sean/pipelines carries the same change (06f46e0).

lint_steps forked TWO subprocesses per scanned line, which cost 29.6s (19.7s of
it kernel spawn time) over sean/pipelines' ~7.9k lines of step manifests. awk
does the same per-line work in one process. dockerfiles mode — the only mode
THIS repo's CI runs — is untouched and verified byte-identical.
KERNEL_REPO_URL still defaulted to
forgejo-http.forgejo-alice.svc.cluster.local. That namespace stopped
existing on 2026-07-23 when the Forgejo singleton was renamed, so every
kernel build since has failed:

  fatal: unable to access '.../sean/linux.git/':
  Could not resolve host: forgejo-http.forgejo-alice.svc.cluster.local

Nobody noticed because no kernel build ran between the rename and today —
the last green one was 2026-07-20. The build that surfaced it was a config
change for Tetragon, which never got as far as compiling anything.

The Shipwright Build passes only KERNEL_BRANCH, DEFCONFIG and LOCALVERSION,
so this ARG default is what every build actually uses; nothing overrode it.

Also stop the retry loop from disguising this class of failure. It exists
because sean/linux is a ~280MB tarball snapshot whose GitMirror import can
still be running when the build fires, so "repo not ready yet" deserves
patience. A Service name that does not resolve deserves none: it is a wrong
name, and no amount of waiting fixes a wrong name. Conflating the two cost
ten minutes per run of "import not ready yet?" — which reads like a slow
import, not a typo, and is precisely why this survived six days and several
red builds.

The host is now resolved once, up front, and an unresolvable one fails
immediately naming the likely cause. The retry keeps its original job.
pipeline-bot deleted branch _promote/9b27b99b0db3 2026-07-29 03:55:31 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sean/builder-images!57
No description provided.