docs(ci-insights): documents how far back CI Insights job history goes - #13038
Merged
Conversation
Contributor
Merge Protections🟢 All 5 merge protections satisfied — ready to merge. Show 5 satisfied protections🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
jd
approved these changes
Sep 28, 2026
Contributor
Merge Queue Status
This pull request spent 3 minutes 1 second in the queue, including 2 minutes 38 seconds running CI. Required conditions to merge
|
49 tasks
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nothing in the documentation said how long CI Insights keeps job data, so the
first time a reader meets the limit is a date range that comes back emptier
than they asked for, with nothing anywhere to explain it. The Jobs page is
where that happens, since it is the page whose whole purpose is looking at a
window of history.
The new section states both numbers: thirty days of history, and twenty-four
hours on the free tier. The distinction matters because the shorter window is
not an error or an ingestion delay — a wider range simply returns nothing past
the cap, which reads exactly like data that never arrived. It also points at
the banner both views already show, so a reader can tell which of the two
windows they are on without guessing.
Evidence: the retention window applied when reading job spans, the shorter
floor the read filters apply without the retention entitlement, and the
product's own copy for the same limit.
Open question: the same cap also shapes the self-hosted runner views, which
read from the same spans. It is stated once, on Jobs, rather than repeated on
Self-hosted Runners; a cross-reference there may be worth adding later.