ci: sticky PR comment with ISO build artifact table#57
Merged
Conversation
Whenever the Test Nix workflow builds full installer/appliance ISOs on a PR, post (and re-update on every rebuild) a single sticky comment with a markdown table of each ISO's kind, architecture, exact size, and download link. - Each matrix build records exact ISO byte sizes to a per-arch TSV and uploads it as a tiny iso-meta-<system> artifact. - A new iso-table job downloads those, maps each ISO artifact to its browser download URL, and upserts a marker-tagged comment so rebuilds update the same message instead of stacking new ones.
📀 ISO build artifacts
↻ Updated for |
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
1 participant
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.
What
Whenever the Test Nix workflow builds full installer/appliance ISOs on a PR, post — and re-update on every rebuild — a single sticky comment containing a cute markdown table of each ISO's kind, architecture, exact size, and download link.
Example rendered comment:
📀 ISO build artifacts
coder-box-appliance-aarch64-linux.isocoder-box-appliance-x86_64-linux.isocoder-box-installer-aarch64-linux.isocoder-box-installer-x86_64-linux.isoHow
stat -c %s) into a per-arch TSV and uploads it as a tiny, 1-dayiso-meta-<system>artifact.iso-tablejob (needs: [plan, Images], gated onpull_request+ at least one full ISO build) downloads those TSVs, maps each ISO artifact to its browser download URL via the Actions API, renders the table, and upserts a comment matched by a hidden<!-- iso-build-table -->marker — so rebuilds update the same message rather than stacking new ones.Notes / scope
pull_requestevents get the comment (usespull-requests: write); drv-only validation runs produce no artifacts and are skipped.qemu/vfkit/Lima/UTM boot helpers.release.ymlalready attaches ISOs with permanent release-asset URLs to the GitHub Release body; left as-is to keep scope tight (could mirror the table into release notes as a follow-up if wanted).