Repository navigation
Fleet status page - #3
Merged
Merged
Conversation
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
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.
Adds /fleet/, a page that shows whether each jlt-commons project builds against its own pinned jolt, jolt's latest release and jolt's nightly. It reads status.json and history.json from the ci-builds status branch in the browser, so the site needs no rebuild when results change.
The page lists failing projects first, in the order the data arrives. Every cell says what happened in words ("pass", "fail at Formatting", "ran on the wrong jolt", "could not run: infra", "not tested yet") and links to its run, so colour is never the only signal. A project whose pin is behind the latest release gets a "pins 0.8.24, latest 0.8.27" note, and each row has a collapsible history. Repos outside the fleet are listed at the bottom with the reasons the check gave. The grid scrolls inside its own container on a phone.
If a fetch fails, the schema is not 1, or the data is more than 12 hours old, the page says so plainly instead of showing a grid that reads as all fine. The last-checked time comes from the newest canary workflow run through the GitHub API, once per load, and shows "unknown" if that call fails. A failed history fetch hides the history strips and says so, but keeps the grid.
The rendering functions are pure and tested with node (test/fleet.test.mjs, 22 tests). site.yml runs them before the build with
node --test test/*.test.mjs. I used the glob becausenode --test test/fails on Node 24. The Check the build allowlist now includes /fleet/, since the home page links to it.Merging publishes the page.
Checked locally with the docs-engine preview and headless Chrome against the live data: seven projects render, no console errors, and at phone width only the grid scrolls.