fix: add retry loop to CI wget for update-kustomize-tag #242

Merged
forgejo_admin merged 1 commit from 230-ci-wget-retry into main 2026-03-28 20:02:24 +00:00

Summary

BusyBox wget has no built-in retry flags. Transient forgejo-http connection failures cause the kustomize tag update step to fail silently. This wraps the wget call in a 5-attempt retry loop with 5s backoff and a fatal guard.

Changes

  • .woodpecker.yaml: Replaced bare wget in update-kustomize-tag step with a retry loop (5 attempts, 5s sleep) and a test -f guard that exits fatally if the script was never downloaded.

Test Plan

  • YAML validated with python3 -c "import yaml; yaml.safe_load(...)"
  • CI pipeline will run on PR to verify no syntax regressions
  • Retry logic exercisable by temporarily breaking the URL in a test branch

🤖 Generated with Claude Code

## Summary BusyBox wget has no built-in retry flags. Transient forgejo-http connection failures cause the kustomize tag update step to fail silently. This wraps the wget call in a 5-attempt retry loop with 5s backoff and a fatal guard. ## Changes - `.woodpecker.yaml`: Replaced bare `wget` in `update-kustomize-tag` step with a retry loop (5 attempts, 5s sleep) and a `test -f` guard that exits fatally if the script was never downloaded. ## Test Plan - YAML validated with `python3 -c "import yaml; yaml.safe_load(...)"` - CI pipeline will run on PR to verify no syntax regressions - Retry logic exercisable by temporarily breaking the URL in a test branch ## Related - Forgejo issue: forgejo_admin/pal-e-platform#230 🤖 Generated with [Claude Code](https://claude.com/claude-code)
BusyBox wget has no retry flags. Transient forgejo-http connection
failures cause the kustomize tag update to fail silently. 5 retries
with 5s backoff.

Ref: forgejo_admin/pal-e-platform#230

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
forgejo_admin deleted branch 230-ci-wget-retry 2026-03-28 20:02:24 +00:00
Sign in to join this conversation.
No description provided.