ci: cache NuGet, cancel superseded runs, test report + coverage summary #198
No reviewers
Labels
No labels
alpha:wave-0
alpha:wave-1
alpha:wave-2
alpha:wave-3
area:assets
area:combat
area:ecology
area:infra
area:render
area:scripting
area:ui
area:world
enhancement
epic
migration
post-alpha
roadmap
tech-debt
type:bug
type:chore
type:design
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
marco/IsoMmo!198
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/pipeline-improvements"
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
CI improvements now that marketplace actions resolve on the Forgejo runner (#193). Favours maintained actions over bespoke shell.
actions/cache) — package folder restored across runs (keyed off the project files); a cache-backend miss degrades to a normal restore.concurrencywithcancel-in-progressonly onpull_request(never main / a releaseworkflow_call).timeout-minutes) so a stuck job fails fast instead of eating the runner.Deferred to #199
The
dorny/test-reporter(posts a check-run) andirongut/CodeCoverageSummary(heavy .NET SDK Docker image) actions were slow/unstable on this Forgejo runner, so they were pulled. Test-result reporting + a per-project coverage gate (the repo-wide 85% number isn't viable — GUI/tool projects sit at 18–70%) move to #199 with Forgejo-compatible tooling.How it was tested
YAML validated; CI green on this PR (the cache/concurrency/timeout changes resolve on the runner).
Checklist
just lint/just testunaffected