Skip to content

Deploy platforms.json to website repo - #359

Merged
lsf37 merged 2 commits into
masterfrom
lsf37/platforms-json-deploy
Nov 3, 2026
Merged

lsf37 merged 2 commits into
masterfrom
lsf37/platforms-json-deploy

Conversation

@lsf37

@lsf37 lsf37 commented Nov 3, 2026 •

Copy link
Copy Markdown
Member

We are already generating a platforms.json file that is consumed in the website repo for an overview of supported platforms. The main missing step was to deploy it automatically, which is now done here.

  • fix platforms.json template: we produced incorrect json if the last entry was a non-maintained platform. Use filters/map + jsonify instead to avoid any future problems of that form.

  • add GitHub deploy step to website repo: copy the generated platforms.json into a sparse checkout of the website repo and push if there are any changes to the current version. (Sparse checkout to avoid 890 MB download)

lsf37 added 2 commits November 3, 2026 11:27
Use Liquid filters instead for the json template so that we don't get
any trailing commas by accident. The previous forloop.last check was
insufficient, because there could be another element in the loop that
will then not be printed, because it is not maintained.

Signed-off-by: Gerwin Klein <[email protected]>
Deploy any changes in the generated platforms.json automatically to the
main seL4 website repo. Do nothing if platforms have not changed.

A successful push will trigger a corresponding rebuild and deploy on the
website repo.

Signed-off-by: Gerwin Klein <[email protected]>
@lsf37
lsf37 requested a review from corlewis November 3, 2026 00:44
@lsf37
lsf37 merged commit 97021d2 into master Nov 3, 2026
10 checks passed
@lsf37
lsf37 deleted the lsf37/platforms-json-deploy branch November 3, 2026 01:53
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.

2 participants