ci: nightly builds no longer exhaust the artifact storage quota - #28
Merged
Conversation
Thread transfer impact
This comment will update automatically after the next completed run. |
Nightly releases have failed every day since 2026-08-12 with "Artifact storage quota has been hit", so the newest desktop build is from 08-11. The org's Team plan includes 2 GB-month of Actions storage, which GitHub meters as 1460 GB-hours. The four desktop-* artifacts total ~915 MB per run, so a daily nightly bills 0.915 * retention_days * 730 GB-hours. The previous 7-day cap bills ~4665 of 1460, over triple the budget, which is why capping retention at a week did not stop the quota from refilling. Drop desktop-* to 1 day (~666 GB-hours, 46% of budget) and give wsl-node-pty-x64 the retention it was missing — it inherited the 90-day repository default despite being consumed by the Windows build in the same run. Both artifacts are intra-run handoffs; the GitHub Release is the durable copy of the installers. Written by Claude Opus 5 in Pylon.
rynfar
force-pushed
the
ci/artifact-retention-budget
branch
from
August 16, 2026 17:14
5e79a89 to
22c4bbc
Compare
23 tasks
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.
Problem
Nightly releases have failed every day since 2026-08-12 — runs 31585789218, 31689516095, and 31790479914 all died at their first artifact upload with:
The schedule fires fine; nothing downstream of the upload ever starts, so the newest desktop build users can get is from 08-11. Every PR merged since then is on
pylonbut unpackaged.26f01c0a2already cappeddesktop-*retention at 7 days for this reason, but the quota refilled anyway, because 7 days was never sized against the actual budget.Fix
The org's Team plan includes 2 GB-month of Actions storage, which GitHub meters as
2 * 730 = 1460GB-hours. The fourdesktop-*artifacts total ~915 MB per run, so a daily nightly bills0.915 * retention_days * 730GB-hours:August peaked at 14.4 GB/day and closed the month's allowance at 1,488 of 1,460 GB-hours.
desktop-*drops to 1 day. It is an intra-run handoff topublish_release, which attaches the installers to the GitHub Release — that Release is the durable copy, and Release assets do not count against Actions storage.wsl-node-pty-x64gets theretention-daysit was missing. It is consumed by the Windows build in the same run but silently inherited the 90-day repository default.resource-monitor-*stays at 7 days: 1.2 MB per run is ~8 MB steady state.Also done outside this PR
Deleted the 143 stale artifacts (933 MB) created before
26f01c0a2, all still on the 90-day default. Live artifact storage is now 0 MB. Verifiedv0.0.33-nightly.20260811.54has all 15 assets attached before deleting its build artifacts.Current verification
pylonvp fmt --check .github/workflows/release.ymlgit diff --checkStill needs a human
This PR caps future growth but cannot refund August's spent allowance, and the Actions spending limit is
$0, so uploads stay blocked until it is raised or the allowance resets on 09-01. Raising the limit is the only thing that unblocks tonight's nightly.Written by Claude Opus 5 in Pylon.
Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.