Validation: basketball-api#281 — Admin CRM parent fields
Ticket
Forgejo issue: basketball-api#281 (Admin CRM parent fields)
Board item: #741
PR: basketball-api#287 — merged to main as commit
What shipped: Added parent_phone/parent_email to admin CRM response models.
Board item: #741
PR: basketball-api#287 — merged to main as commit
ba8bffbWhat shipped: Added parent_phone/parent_email to admin CRM response models.
Environment
Production cluster (k3s on archbox). Namespace:
basketball-api. ArgoCD app: basketball-api (Synced, Healthy).Checks
| # | Criterion | How to Verify | Result | Evidence |
|---|---|---|---|---|
| 1 | Pipeline green on main | Woodpecker pipeline #304 (push for PR #287 merge) | FAIL | Pipeline #304 status: failure. Test step failed (exit_code 1). build-and-push succeeded but update-kustomize-tag was skipped. |
| 2 | Image deployed to pod | kubectl get pod -n basketball-api | FAIL | Running image: <code>92e047e8f13e...</code> (from PR #306 era). PR #287 commit <code>ba8bffb</code> is NOT deployed. Kustomize tag was never updated because pipeline test step failed. |
| 3 | Pod healthy | kubectl get pod | PASS | Pod <code>basketball-api-7bcd498994-pt9zf</code> Running, 1/1 Ready. But running old image. |
Verdict
FAIL — Pipeline test failures on main block deployment. The code is merged but not deployed. All 6 basketball-api PRs (#287-#292) share this same blocker: Woodpecker pipelines #304-#310 all fail at the test step, causing update-kustomize-tag to be skipped. The running pod still has image tag
92e047e.Discovered Issues
- BLOCKER: basketball-api CI pipeline tests are failing on main since at least pipeline #297. This blocks all deployments. Test failures need investigation and a fix PR before any of the 6 tickets can be validated as deployed.