9efb733974
All checks were successful
build-and-release / build (catering-services) (push) Successful in 49s
build-and-release / build (cron) (push) Successful in 49s
build-and-release / build (developers) (push) Successful in 39s
build-and-release / build (employees) (push) Successful in 38s
build-and-release / build (fitness-trainers) (push) Successful in 38s
build-and-release / build (gateway) (push) Successful in 38s
build-and-release / build (graphic-designers) (push) Successful in 38s
build-and-release / build (job-seekers) (push) Successful in 39s
build-and-release / build (jobs) (push) Successful in 39s
build-and-release / build (leads) (push) Successful in 39s
build-and-release / build (makeup-artists) (push) Successful in 39s
build-and-release / build (companies) (push) Successful in 6m56s
build-and-release / build (payments) (push) Successful in 39s
build-and-release / build (customers) (push) Successful in 6m33s
build-and-release / build (social-media-managers) (push) Successful in 39s
build-and-release / build (ugc-content-creators) (push) Successful in 39s
build-and-release / build (users) (push) Successful in 39s
build-and-release / build (video-editors) (push) Successful in 39s
build-and-release / build (photographers) (push) Successful in 6m28s
build-and-release / build (tutors) (push) Successful in 6m32s
Confirmed via the matrix run: every service's actual docker build and push succeeded, but the GitOps-update step failed on all of them with "GITOPS_PUSH_TOKEN is empty". Checked the repo's configured secrets - GITOPS_PUSH_USERNAME/GITOPS_PUSH_TOKEN were never set; only a leftover GITOPS_GITHUB_USERNAME/GITOPS_GITHUB_TOKEN pair (from before the gitops repo moved to Forgejo) and GITOPS_PAT exist. Confirmed ashwin/nxtgauge-gitops lives on ci.nxtgauge.com matching this workflow's defaults, so GITOPS_PAT is the one meant for this. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| build.yaml | ||