Add .woodpecker.yaml CI pipeline #6

New issue

Closed

opened 2026-05-24 13:59:59 +00:00 by ldraney · 0 comments

ldraney commented

2026-05-24 13:59:59 +00:00

Owner

Type

Feature

Context

Palinks needs a Woodpecker CI pipeline to build the Docker image and push to Harbor on every push to main. The Dockerfile already exists and builds a multi-stage Ruby/Rails image with Thruster on port 80.

Acceptance Criteria

.woodpecker.yaml added with Kaniko build step
Triggers on push to main only
Uses in-cluster Forgejo clone (forgejo-http.forgejo.svc)
Pushes to harbor.tail5b443a.ts.net/palinks/app:$COMMIT_SHA
Layer cache at harbor.tail5b443a.ts.net/palinks/cache
Woodpecker secrets configured: harbor_username, harbor_password (from Harbor CI robot created by pal-e-services terraform)

Reference

See docs/pipeline.md in this repo for the exact pipeline spec.

### Type Feature ### Context Palinks needs a Woodpecker CI pipeline to build the Docker image and push to Harbor on every push to main. The Dockerfile already exists and builds a multi-stage Ruby/Rails image with Thruster on port 80. ### Acceptance Criteria - [ ] `.woodpecker.yaml` added with Kaniko build step - [ ] Triggers on push to main only - [ ] Uses in-cluster Forgejo clone (forgejo-http.forgejo.svc) - [ ] Pushes to `harbor.tail5b443a.ts.net/palinks/app:$COMMIT_SHA` - [ ] Layer cache at `harbor.tail5b443a.ts.net/palinks/cache` - [ ] Woodpecker secrets configured: `harbor_username`, `harbor_password` (from Harbor CI robot created by pal-e-services terraform) ### Reference See `docs/pipeline.md` in this repo for the exact pipeline spec.