Woodpecker: expose bundle-cache PVC volume to pipeline pods #417
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#417
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
Feature
Lineage
Standalone — supports landscaping-assistant#187 pipeline optimization.
Repo
pal-e-platform
User Story
As a CI pipeline, I need access to a persistent gem cache so bundle-install runs in ~10s instead of ~90s.
Context
landscaping-assistant PR #188 added PVC-backed gem caching to
.woodpecker.yaml. The PVCwoodpecker-bundle-cachehas been created in the cluster. The Woodpecker agent needsWOODPECKER_BACKEND_K8S_VOLUMESset so pipeline pods can mount it.Description
Add one env var to the Woodpecker agent in
terraform/modules/ci/main.tf:File Targets
terraform/modules/ci/main.tf(1 line added)Feature Flag
None.
Acceptance Criteria
terraform applyrolls the agent with the new configTest Expectations
After
terraform apply, next landscaping-assistant pipeline should populate the gem cache on first run and use it on subsequent runs.Constraints
kubectl apply). Future: manage via Terraform resource.Checklist
terraform applyrun on infra hostRelated