Document Forgejo runner CI lane requirements in docs/ci/lanes.md #39

New issue

Closed

opened 2026-05-25 09:05:58 -03:00 by navigator · 2 comments

navigator commented

2026-05-25 09:05:58 -03:00

Owner

Goal

Create docs/ci/lanes.md documenting the four-tier CI lane structure from PLAN.md Section 12.6 as contributor-facing reference. This complements (does not modify) the actual workflow YAML in .forgejo/workflows/** which is off-limits per ADR-017.

Document must cover for each lane:

Lane name and trigger (push / PR / nightly / weekly)
Time budget (5min / 30min / 4h / 24h)
Expected jobs (compile/lint, chiseltest units, Verilator builds + baseline bench, 8-chip + BER + formal)
Runner target (2804:710:d0:5::10)
Failure escalation policy (block merge on fast/standard fails; nightly/weekly file issue rather than block)
How contributors check lane status

Acceptance criteria

docs/ci/lanes.md exists with table summarizing the four lanes
Time budgets match Section 12.6 exactly
Document explicitly notes that workflow YAML lives under .forgejo/workflows/** and is owned by Marcos (off-limits per ADR-017)
Cross-references the verification test-strategy doc (already an open issue)
Does NOT touch any .forgejo/workflows/** file
Adds docs/ci/README.md if missing

Plan refs

Section 12.6 (CI lanes), Section 12.7 (sign-off criteria as motivation)

Notes

This is documentation only. Marcos retains exclusive control over the actual workflow YAML. The doc describes intent; reality may differ until workflows are written, in which case the doc should be updated to match.

## Goal Create `docs/ci/lanes.md` documenting the four-tier CI lane structure from PLAN.md Section 12.6 as contributor-facing reference. This complements (does not modify) the actual workflow YAML in `.forgejo/workflows/**` which is off-limits per ADR-017. Document must cover for each lane: - Lane name and trigger (push / PR / nightly / weekly) - Time budget (5min / 30min / 4h / 24h) - Expected jobs (compile/lint, chiseltest units, Verilator builds + baseline bench, 8-chip + BER + formal) - Runner target (`2804:710:d0:5::10`) - Failure escalation policy (block merge on fast/standard fails; nightly/weekly file issue rather than block) - How contributors check lane status ## Acceptance criteria - [ ] `docs/ci/lanes.md` exists with table summarizing the four lanes - [ ] Time budgets match Section 12.6 exactly - [ ] Document explicitly notes that workflow YAML lives under `.forgejo/workflows/**` and is owned by Marcos (off-limits per ADR-017) - [ ] Cross-references the verification test-strategy doc (already an open issue) - [ ] Does NOT touch any `.forgejo/workflows/**` file - [ ] Adds `docs/ci/README.md` if missing ## Plan refs Section 12.6 (CI lanes), Section 12.7 (sign-off criteria as motivation) ## Notes This is documentation only. Marcos retains exclusive control over the actual workflow YAML. The doc describes intent; reality may differ until workflows are written, in which case the doc should be updated to match.