Push separate :base and :build tags from ruby-arch pipeline #368
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ldraney/pal-e-platform#368
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Bug
Context
Discovered during T4 validation (
validation-18-2026-05-10). The ruby-arch Woodpecker pipeline only pushes:latest, which Kaniko builds as the last Dockerfile stage (build). This means::latest= build stage (includes base-devel, git, pkgconf — ~100MB of compilers):basetag exists for the runtime-only stageDownstream Dockerfiles (pal-enterprises) must use
:latestfor both their base and build stages, resulting in bloated runtime images that include unnecessary compilers.Proposed Fix
Split the Kaniko step into two:
--target=base, push as:base(and:latestfor backwards compat)--target=build, push as:buildOr use two separate Kaniko steps in
.woodpecker/ruby-arch.yaml.Acceptance Criteria
harbor.tail5b443a.ts.net/pal-e/ruby-arch:baseexists and does NOT include base-develharbor.tail5b443a.ts.net/pal-e/ruby-arch:buildexists and includes base-devel:latestpoints to:base(runtime image should be the default):baseand:buildexplicitly