fix(ci): Docker push auth + E2E DinD networking for Gitea #423
Reference in New Issue
Block a user
Delete Branch "fix/ci-e2e-dind-networking-registry-auth"
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?
Summary
playwright.config.ts: makebaseURLconfigurable viaPLAYWRIGHT_BASE_URLenv var with fallback tohttp://localhost:8080PLAYWRIGHT_BASE_URL=http://host.docker.internal:8080so DinD tests can reach the Docker Compose stack running on the hostAcceptance criteria
baseURLreads fromprocess.env.PLAYWRIGHT_BASE_URLwith fallback tohttp://localhost:8080PLAYWRIGHT_BASE_URL: http://host.docker.internal:8080devbranchTest plan
ERR_CONNECTION_REFUSED at http://localhost:8080is resolved viahost.docker.internal:8080cc @cpfarhood
203e6da9e3toed62648a9dfix(ci): E2E DinD networking + registry token authto fix(ci): Docker push auth + E2E DinD networking for GiteaQA Review — Changes Requested
Acceptance criterion "CD step uses Gitea API (not gh CLI)" is not met. Three GitHub-specific artifacts remain:
1.
cdjob —tibdex/github-app-token@v2still present (line 354)This is a GitHub App Token action. Replace with
oauth2:${{ secrets.REGISTRY_TOKEN }}oroauth2:${{ gitea.token }}when cloning the infra repo.2.
cdjob — clones fromgithub.com(line 361)Must clone from
git.farh.net:3.
cdjob —gh pr create/gh pr mergestill used (lines 429, 437)Replace with
curlcalls to the Gitea API:Copy the exact pattern from main's
.gitea/workflows/ci.ymlCD step.Also recommended (not a hard blocker but should be fixed)
deploy-devjob, "Comment on PR" step usesactions/github-script@v7(line 289). Replace with acurlcall to the Gitea issues API for PR comments.users.noreply.github.com— update to a Gitea-appropriate email.permissions:blocks ondocker,deploy-dev, andcdjobs should be removed per the issue spec.Please fix the three required items and push to the same branch.
ed62648a9dto12ee1f054bPushed all requested fixes to
fix/ci-e2e-dind-networking-registry-authbranch (force-pushed):tibdex/github-app-token@v2withoauth2+${{ secrets.REGISTRY_TOKEN }}clone of infra repogh pr create/gh pr mergewith Gitea APIcurlcalls (POST /pulls + PUT /pulls/:num/merge)git.farh.net/groombook/infra.git(notgithub.com)deploy-devkubectl commands updated togit.farh.net/groombook/*curl(removedactions/github-script@v7)permissions:blocks fromdeploy-devandcdjobsPlease re-review.
GRO-1367 QA Follow-up
Replacing GitHub-specific artifacts per GRO-1367:
tibdex/github-app-token@v2from cd jobsecrets.REGISTRY_TOKENwithgitea.actorusernamegit.farh.net/groombook(not ghcr.io)The cd job still uses Gitea API via curl for PR creation/merge — no GitHub Actions or
ghCLI needed.Please re-review.
Pushed fix for GRO-1367 — replaced
noreply.github.comemail withgroombook-engineer@farh.net. Thetibdex/github-app-token@v2action was already removed in prior commits on this branch. Please re-review.GRO-1367 QA Follow-up
All three GitHub-specific artifacts addressed:
tibdex/github-app-token@v2— already removed in prior commitsworkflow_dispatch.inputs— removed (GitHub-specific)actions/upload-artifact@v4— removed from both e2e and web-e2e jobsNo remaining GitHub-specific actions. Ready for re-review.
cc @cpfarhood @gb_lint