ci: add missing timeout-minutes and concurrency guards #12

Merged
admin merged 1 commits from ci/timeout-and-concurrency-guards into main 2026-09-27 02:30:50 +00:00
Owner

Part of a fleet-wide CI-speed pass.

What changed in .gitea/workflows/ci.yml:

  • Added timeout-minutes to all three jobs, which had none: quality (30), contracts (30) — both install/typecheck/test/build style jobs — and security (15), a single Trivy scan. Without this, a hung step could tie up a runner indefinitely.
  • Added a top-level concurrency block (group keyed on workflow + ref, cancel-in-progress: true). This workflow triggers on both push (unfiltered) and pull_request, so every PR commit was running the full CI suite twice. The concurrency group cancels the superseded run instead of changing what triggers CI. Same pattern already used in admin/serv0, admin/s0cial, admin/ppl0, admin/pers0n.

masterplan-lock.yml is schedule-only (not on the push/PR hot path) and was left untouched.

No triggers, job logic, caching, matrix, or needs: were changed.

🤖 Generated with Claude Code

Part of a fleet-wide CI-speed pass. What changed in `.gitea/workflows/ci.yml`: - Added `timeout-minutes` to all three jobs, which had none: `quality` (30), `contracts` (30) — both install/typecheck/test/build style jobs — and `security` (15), a single Trivy scan. Without this, a hung step could tie up a runner indefinitely. - Added a top-level `concurrency` block (group keyed on workflow + ref, `cancel-in-progress: true`). This workflow triggers on both `push` (unfiltered) and `pull_request`, so every PR commit was running the full CI suite twice. The concurrency group cancels the superseded run instead of changing what triggers CI. Same pattern already used in admin/serv0, admin/s0cial, admin/ppl0, admin/pers0n. `masterplan-lock.yml` is schedule-only (not on the push/PR hot path) and was left untouched. No triggers, job logic, caching, matrix, or `needs:` were changed. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
admin added 1 commit 2026-09-27 02:29:28 +00:00
ci(workflows): add job timeout-minutes and concurrency guard
CI (SIAX Cloud) / security (push) Successful in 18s
CI (SIAX Cloud) / security (pull_request) Successful in 21s
CI (SIAX Cloud) / contracts (pull_request) Successful in 26s
CI (SIAX Cloud) / quality (push) Successful in 1m10s
CI (SIAX Cloud) / quality (pull_request) Successful in 1m11s
CI (SIAX Cloud) / contracts (push) Successful in 1m24s
d362852384
Part of a fleet-wide CI-speed pass. ci.yml's three jobs (quality,
security, contracts) had no timeout-minutes, so a hung step could run
indefinitely and tie up a scarce runner. Added 30min for the
build/test jobs (quality, contracts) and 15min for the single-check
security scan (Trivy).

ci.yml also triggers on both push and pull_request with no branch
filter, which fires the full CI suite twice per PR commit. Added the
same concurrency group pattern already used elsewhere in the fleet
(admin/serv0, admin/s0cial, admin/ppl0, admin/pers0n) to cancel the
superseded run instead of changing the triggers themselves.

masterplan-lock.yml is schedule-only and not on the hot path, so left
untouched.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
siax-bot approved these changes 2026-09-27 02:29:34 +00:00
admin merged commit dde8a737ce into main 2026-09-27 02:30:50 +00:00
Sign in to join this conversation.
No Reviewers
No labels
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: admin/c0py#12