3afe885cc0
Make checkout idempotent for reused runner workspaces and add a safe test-tag path that validates builds without pushing images or calling the deploy webhook. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1.4 KiB
1.4 KiB
CI build notes
2026-04-24
- Observed failure while reproducing workflow checkout locally: the
Checkout codestep rangit remote add origin ...unconditionally. In a workspace that already had anoriginremote, the job failed witherror: remote origin already exists.and exited beforedocker 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.ymlto initialize Git only when needed, usegit remote set-url origin ...whenoriginalready exists, and force-clean the workspace after checking outFETCH_HEAD. - Safety improvement for remote validation: tags ending with
-testnow run the build verification path only. They skip registry login, image push,latestupdates, and the deploy webhook so act_runner can be tested without deployment side effects. - Current local result:
npm run lint,npm run test -- --runInBand,npm run build,docker build ..., andnpm run buildinsidegitea/runner-images:ubuntu-22.04all completed successfully after the workflow adjustment. - Non-blocking note: local Jest run reported a haste-map naming collision between
package.jsonand.next/standalone/package.json; tests still passed, and this does not affect the current image-build workflow.