Skip to content

ci: increase flux-local helm retry budget to 5×30s #601

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ExtraToast wants to merge 1 commit into from
Closed

ci: increase flux-local helm retry budget to 5×30s #601

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion platform/scripts/validate/render-flux.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,14 @@ echo "==> flux-local expand HelmReleases against remote charts"
# controller does post-merge. Remote chart downloads occasionally return
# transient GitHub/registry 5xx responses; retry only this network-heavy
# step so real template/schema errors still fail deterministically.
retry 3 10 flux-local build all \
#
# flux-local passes --repository-cache /tmp/<random> to every helm
# invocation, so GitHub Actions cache and HELM_CACHE_HOME are both
# bypassed — chart tarballs are always fetched fresh. The only knob
# available is the retry budget. GitHub release CDN 504s typically
# clear within 60-90 s; 5 attempts × 30 s = ~2 min retry window
# covers the observed failure mode without burning excessive CI time.
retry 5 30 flux-local build all \
--enable-helm \
"${flux_root}" \
>> "${render_output}"
Expand Down
Loading