ci: retry firmware uploads on transient 5xx - #13
Merged
Conversation
GitHub's Releases API returned a 502 ("Unicorn!" page) on the first
publish run after PR #12 merged, requiring a manual re-run. Wrap
gh release upload in a 5-attempt loop with linear backoff (10s, 20s,
30s, 40s) so the next blip self-heals. Real auth/scope failures still
surface — they just take ~100s to give up.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
publishrun after PR ci: publish u-boot artifacts to OpenIPC/firmware on master #12 merged failed because the GitHub Releases API returned a 502 "Unicorn!" page on the very firstgh release uploadcall. A manual re-run worked. Add retry to make this self-heal.gh release uploadin a 5-attempt loop with linear backoff (10s, 20s, 30s, 40s — ~100s total before giving up). Real auth/scope failures still fail the job; they just take longer to surface.Test plan