Validation: CI pipeline (issue #22)
Verdict: PASS
Ticket
forgejo_admin/twitch-2k-wager#22 — CI pipeline: Woodpecker build + Harbor push
Board item #801 on board-twitch-2k-wager
Environment
Woodpecker CI, repo: forgejo_admin/twitch-2k-wager, pipeline #13
Checks
| # | Criterion | How Verified | Result | Evidence |
|---|---|---|---|---|
| 1 | Pipeline #13 all 7 steps success | mcp__woodpecker__get_pipeline_status(repo=forgejo_admin/twitch-2k-wager, number=13) | PASS | All 7 steps success (exit_code 0): clone, install, check, test, build, build-and-push, update-kustomize-tag. Event: push on main. Message: "fix: lazy Stripe client init (#35)" |
| 2 | Image pushed to Harbor | Woodpecker build-and-push step logs | PASS | Pushed harbor.harbor.svc.cluster.local/playme2k/app:82768f26b658dd717e624645d6b1364d76a7f668 (sha256:1a878cbed8749b648b226d516f137dc9034fbd8d48ee48ef058bc7e63c521515) |
| 3 | Kustomize tag updated | Woodpecker update-kustomize-tag step logs | PASS | Updated overlays/twitch-2k-wager/prod/kustomization.yaml newTag from "latest" to "82768f26b658dd717e624645d6b1364d76a7f668". Commit 32b4084 pushed to pal-e-deployments main. |
Regression Check
Pipeline is self-contained. No impact on other repos or pipelines.
Discovered Issues
- Note: CI pushes to harbor.harbor.svc.cluster.local (internal) but kustomize references harbor.tail5b443a.ts.net (external). Both should resolve to the same registry, but the Harbor project "playme2k" is not visible via the external API — this is a service-onboarding (issue #1) gap, not a CI gap. The CI pipeline itself did its job correctly.