TJWaterFrontend_Refine/memery.md

CI build notes

2026-04-24

• Observed failure while reproducing workflow checkout locally: the Checkout code step ran git remote add origin ... unconditionally. In a workspace that already had an origin remote, the job failed with error: remote origin already exists. and exited before docker build.
• Why this matters for act_runner: self-hosted Gitea runners can reuse working directories or start from repositories that already contain Git metadata, so checkout logic must be idempotent.
• Applied fix: changed .gitea/workflows/package.yml to initialize Git only when needed, use git remote set-url origin ... when origin already exists, and force-clean the workspace after checking out FETCH_HEAD.
• Safety improvement for remote validation: tags ending with -test now run the build verification path only. They skip registry login, image push, latest updates, and the deploy webhook so act_runner can be tested without deployment side effects.
• Root cause found on the real act_runner: although the runner was registered with ubuntu:docker://gitea/runner-images:ubuntu-22.04, the workflow used runs-on: ubuntu, and the job log showed Start image=ubuntu:latest. That default image does not include the expected toolset, which explains the remote git: not found failure.
• Applied fix for label selection: changed both jobs to runs-on: "ubuntu:docker://gitea/runner-images:ubuntu-22.04" so Gitea resolves the exact runner image instead of falling back to ubuntu:latest.
• Follow-up from server validation: Gitea then reported No matching online runner with label: ubuntu:docker://gitea/runner-images:ubuntu-22.04. The runner advertises the short label ubuntu-22.04, so the workflow was updated again to use runs-on: ubuntu-22.04, which should map to docker://gitea/runner-images:ubuntu-22.04 on the runner side.
• Current local result: npm run lint, npm run test -- --runInBand, npm run build, docker build ..., and npm run build inside gitea/runner-images:ubuntu-22.04 all completed successfully after the workflow adjustment.
• Non-blocking note: local Jest run reported a haste-map naming collision between package.json and .next/standalone/package.json; tests still passed, and this does not affect the current image-build workflow.