Add Woodpecker CI pipeline and k8s manifests #3
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/gcal-scheduler#3
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?
Plan
plan-2026-02-25-mcp-gateway-migration— Phase 3Repo
gcal-scheduler— the repo where the code change happensUser Story
As a platform operator
I need Woodpecker CI and k8s manifests for gcal-scheduler
So that the appointment booking service can be deployed via GitOps alongside the other pal-e services
Acceptance Criteria
When I push to main
Then Woodpecker CI runs lint/test/build and pushes a container image to Harbor
When ArgoCD syncs
Then the gcal-scheduler deployment runs in k8s with correct env vars and health probes
Additional Information
Supersedes #1 / PR #2 with a cleaner implementation that follows the proven pattern from notion-mcp-remote (main branch). Key improvements:
.woodpecker.yaml(not.yml)strategy: Recreateand proper labelsChecklist
Related
project-pal-e— which project this affects