Disable unreliable Gitea Godot cache steps
Full build / Import + headless tests (push) Successful in 35s
Full build / Full desktop build + optional release (push) Skipped

Gitea cache restores were inconsistent and cache saves timed out or were
rejected as reserved by another job. Remove the cache steps and keep direct
4.7.2 downloads; document the evaluation and when to retry. The workflow is
otherwise clean (no .github/ci.yml exists).
This commit is contained in:
zwitschi committed 2026-11-02 09:51:59 +01:00
1 parent 9b8f513f9f
commit fbd2ab2cb3
5 files changed
+20 -53

No files matched your search

+6 -5
View File
@@ -63,11 +63,12 @@ setup, so do not rely on it.
> artifacts. If CI publishing fails again, run
> `./tools/publish_release.sh <version>` from a checkout with `~/.git-credentials`.
> **Godot cache:** the workflow uses Gitea Actions cache for the Godot binary and a
> trimmed 4.7.2 export-template set (Linux/Windows/macOS/Web release files only, not
> Android/iOS). The first run still downloads them; subsequent runs restore from cache.
> If the host cache service is unavailable, remove the cache steps and let the install
> steps download fresh copies.
> **Godot cache evaluation:** Gitea Actions cache was tested for the Godot binary and
> trimmed 4.7.2 templates. Restores worked intermittently, but cache saves timed out
> in `CreateCacheEntry` / were rejected as reserved by another job. The cache steps
> were removed because they added restore/save overhead without a reliable hit.
> Revisit when the host's Gitea Actions cache service is healthy; otherwise keep
> downloading the binary/templates directly.
> The workflow lives in `.gitea/workflows/` (Gitea's canonical path). The old
> `.github/workflows/ci.yml` was removed to avoid double runs on hosts that scan
+1 -1
View File
@@ -188,7 +188,7 @@ Future options include external analytics, cloud saves, or replay sharing, but t
A continuous-integration pipeline keeps the headless test suite green on every change and publishes tagged releases.
- **Workflow:** `.gitea/workflows/build.yml` runs on pushes, pull requests, tags, and manual dispatches. The `checks` job restores/caches Godot 4.7.2, imports the project, and runs `res://src/test/test_runner.gd`; it fails on a non-zero exit code or any `SCRIPT ERROR` in the output.
- **Workflow:** `.gitea/workflows/build.yml` runs on pushes, pull requests, tags, and manual dispatches. The `checks` job installs Godot 4.7.2, imports the project, and runs `res://src/test/test_runner.gd`; it fails on a non-zero exit code or any `SCRIPT ERROR` in the output.
- **Build job:** runs for tags and manual dispatches. It installs export templates, exports Linux/Windows/macOS and the non-threaded Web build, packages the NSIS installer, Linux AppImage and optional Desktop HQ zip, verifies the installer contents, and uploads the artifacts.
- **Publish job:** tag builds call `tools/publish_release.sh` to create the Gitea release and upload the standard artifacts plus the optional Desktop HQ zip. The script uses `GITEA_TOKEN` when configured and otherwise reuses the runner's checkout extraheader credentials.
- **Hosting:** the repository lives on Gitea (`https://git.allucanget.biz/zwitschi/security-game`). Export templates must match the pinned Godot version; macOS builds are unsigned and need quarantine guidance or notarization for wider distribution.