Add Arch Linux Ruby base image with weekly rebuild pipeline #361
No reviewers
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ldraney/pal-e-platform!361
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "360-arch-ruby-base-image"
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?
Summary
Changes
docker/ruby-arch/Dockerfile: Multi-stage base image.basestage installs ruby, jemalloc, postgresql-libs, libyaml, and bundler via gem.buildstage adds base-devel, git, pkgconf for native gem compilation.docker/ruby-arch/.woodpecker.yaml: Kaniko-based pipeline matching sibling repo conventions (basketball-api, pal-e-docs). Triggers on manual + cron events, pushes topal-e/ruby-arch:latest.Test Plan
ruby --versionin container returns current Arch Rubybundler --versionworksgem install pgworks in build stageLD_PRELOAD=/usr/lib/libjemalloc.so ruby -e "puts :ok"succeedsReview Checklist
Related Notes
ldraney/pal-e-platform #360-- Arch Linux Ruby base image in Harbor with weekly rebuild pipelineCloses #360
Tofu Plan Output (full)
PR Review -- #361
Dockerfile (
docker/ruby-arch/Dockerfile)PASS -- clean and correct.
ruby,jemalloc,postgresql-libs,libyaml,pkgconf,base-devel)gem install bundler(correct -- avoids pacman version pinning mismatch)pacman -Scc+rm -rf /var/cache/pacman/pkg/*)LD_PRELOADfor jemalloc is set correctlybasefor runtime,buildextends with dev toolingPipeline (
docker/ruby-arch/.woodpecker.yaml)PASS with note -- Kaniko pattern matches sibling repos exactly.
.netrcneeded since no private repo access during build)registry,insecure,extra_opts,from_secret) match basketball-api and pal-e-docs patterns exactlydockerfileandcontextpaths are correctly set for the nested locationfrom_secret(no hardcoded credentials)manualandcronNote: The pipeline file lives at
docker/ruby-arch/.woodpecker.yaml, not at the repo root or in.woodpecker/. Woodpecker will NOT auto-discover this file. This is fine -- the cron job in the Woodpecker UI must specify the pipeline config path (docker/ruby-arch/.woodpecker.yaml). This should be documented in the manual gates section, which it partially is.SOP Compliance
360-arch-ruby-base-imagefollows{issue-number}-{kebab-case-purpose}Closes #360present for auto-closeVERDICT: PASS