Write down how CI works, while it is finally knowable #1077
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1077
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/ci-pipeline"
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?
There is no page describing the pipeline. Everything about it — which checks run, what cancels what, why jobs carry timeouts, how to reproduce a failure locally — has lived in commit messages and in the head of whoever last debugged it. That was survivable while the honest answer was "it is broken". Now that it moves, the answers are worth keeping.
docs/CI.mdcovers:.github/workflows/is gone (#1059)pull_request.number || sha(#1076)maintrailing on a busy day, throughput ceiling, scheduled runs competing in the same queueIt is written from the workflows themselves and says so: if the page and the workflow disagree, the workflow is right and the page is a bug.
CONTRIBUTING.mdlinks it from both places a contributor meets CI — the rules list and the review process — because "all checks must pass" without saying which checks is not an instruction.8eab33f033c5535f4929Corrected the runner table after a longer sample: ~50 s mean job duration at capacity 1, ~63 s at capacity 2 — the second slot costs about a quarter of a job, so the real gain is ~1.6x, not 2x. The page now says that, and says to watch memory rather than CPU next time.
83e224771626633dc39b