Skip to content

ci: cap GHA timeouts (job <=5m, step <=3m)#13

Merged
kirill-abblix merged 1 commit into
masterfrom
ci/gha-timeout-caps
May 25, 2026
Merged

ci: cap GHA timeouts (job <=5m, step <=3m)#13
kirill-abblix merged 1 commit into
masterfrom
ci/gha-timeout-caps

Conversation

@kirill-abblix
Copy link
Copy Markdown
Member

Summary

  • Apply Abblix billing-protection policy: timeout-minutes: 5 on jobs, 3 on steps.
  • Affirm concurrency.cancel-in-progress: true (already present).

Context

May 2026 GHA usage hit the org limit. 5m/3m caps are intentionally tight; known-long jobs may need deliberate lift after CI resumes.

Test plan

  • actionlint check passes
  • Untrusted-input interpolation check passes
  • Merge after CI resumes in June (currently billing-frozen)

…l-in-progress

Bulk-apply billing-protection policy across all workflows:
- Top-level concurrency: cancel-in-progress: true (already present in all
  files; this commit affirms the policy)
- Job-level timeout-minutes: 5 (overrides higher; preserves lower)
- Step-level timeout-minutes: 3 (overrides higher; preserves lower)

Context: May 2026 GHA usage hit the org limit. 5m/3m caps are
intentionally tight -- known-long jobs (release pipelines, full test
suites) will need deliberate per-job lift after CI resumes in June.

Tooling: ruamel.yaml round-trip preserved comments + key order.
@kirill-abblix kirill-abblix merged commit c2617cf into master May 25, 2026
2 checks passed
@kirill-abblix kirill-abblix deleted the ci/gha-timeout-caps branch May 25, 2026 08:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant