Files
endorphin-tessera-gui/.gitea/workflows/README.md
T
2026-10-23 22:35:00 +08:00

2.6 KiB

Tessera GUI workflows

ci.yml verifies this project on main pushes, pull requests and manual dispatch. It runs on ces-control, with a 60-minute timeout. HTTPS checkout and job token details are in the parent README.

There is no production service deployment in this workflow.

The container includes the Endor examples used by the live guide and tests. It validates the actual Aster-backed source-to-UI path, snapshot lifetime, layout and execution budgets, failed-update preservation and stale-result invalidation, in addition to the existing rendering checks and Clippy. Cargo uses official sources. The primary example now executes top-level let statements and ui.page().render through Aster's Interactive interface. Function-entry compatibility, original source positions, page methods and page budgets are also checked. The workflow checks the macOS packaging script's syntax without running it on Linux. Docker is used only in this remote workflow; local compilation is native.

The test image installs DejaVu Sans/Mono and Noto CJK for font metrics and Chinese fallback checks. Text regression tests inspect glyph selection, measured advances, fractional scale, multiline bounds, Unicode truncation and antialiased opacity.

Incremental verification

Gitea 1.26 concurrency groups cancel superseded runs on the same ref. Markdown-only pushes and pull requests skip verification; executable Endor examples and Rust files (including embedded guide strings) still trigger checks. Manual dispatch always runs verification. Existing queued runs created from older workflow revisions retain their old behavior.

The workflow invokes verify-ci.sh. Docker builds the Rust 1.91.1/system/font toolchain from Dockerfile.ci over stdin, without sending a source build context. The checkout is mounted read-only at /build. Named volumes persist Cargo registry/git downloads and /cargo-target across container removal, including failed tests and cancelled runs. Main/manual runs and each PR have separate cache scopes. Changing Rust/toolchain compatibility requires updating the image and cache prefix in the script. Cargo lockfiles and fingerprints decide which dependencies/artifacts are reusable; caches do not bypass checks.

A host flock serializes each scope's writable target cache. Signal handling removes only the current run's named container; it never prunes shared Docker resources or deletes cache volumes. The first run populates caches; later runs still execute fmt, all tests and Clippy. Cargo compilation remains single-job to limit memory pressure on the shared host. No CPU-time guarantee is implied.