Build and publish releases on one runner with parallel transfers - #374
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
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.
Release run 36834231719 spent 7m22s building and 10m39s publishing, including 2m41s downloading the 3.54 GB release artifact into a second runner. Build and publish in the same GitHub-hosted Ubuntu 22.04 job after the required checks, using local assets directly. Retain the Actions artifact before publication for recovery. The combined job has contents/packages write permissions, explicitly approved by the maintainer.
Use deterministic level-6 pigz compression with up to four workers for Runtime/control/offline archives. Upload up to four Release assets concurrently, largest first, and push up to four GHCR images concurrently after all local image and existing-tag preflight checks. Keep fixed draft IDs, complete inventory verification, tag rechecks, and no write retries. Failures leave the Release unpublished and wait for in-flight transfers to finish.
Retain Go/pnpm caches and cache npm downloads plus the checksum-verified microsandbox archive. Cache reuse remains subject to GitHub ref scoping. Update original-artifact recovery instructions for the combined job. Restrict check-docs to its five documentation tests; full distribution checks retain all packaging coverage and install pigz.
Validation (focused on this change):
No live publication or full Linux distribution build was executed locally. The removed download cost is measured from the cited run; total speedup and the effect of switching runner providers need a real release run.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.