Skip to content

fix(release): retry transient Gitee tag pushes - #856

Draft
haofeng0705 wants to merge 1 commit into
mainfrom
codex/fix-gitee-tag-push-retries
Draft

fix(release): retry transient Gitee tag pushes#856
haofeng0705 wants to merge 1 commit into
mainfrom
codex/fix-gitee-tag-push-retries

Conversation

@haofeng0705

Copy link
Copy Markdown
Collaborator

What changed

  • retry a missing immutable Gitee tag push up to three times
  • bound each push attempt to 75 seconds with a 5-second delay
  • increase the tag-stage deadline from 300 to 360 seconds while preserving the overall release budget
  • verify the exact remote commit after every failed/timed-out push before retrying
  • add a regression test for a transient first-push failure

Why

Recent Gitee repairs for v1.0.55-beta.7 and v1.0.56-beta.3 passed GitHub release authority and artifact verification, but each made only one tag push. The push stalled until the old timeout and the repair failed without a safe retry.

The new flow remains fail-closed: it never moves an existing tag and accepts a timed-out/concurrent push only when the remote tag resolves to the exact expected commit.

Validation

env GOCACHE=/tmp/dws-go-cache GOPATH=/tmp/dws-go-path GOMODCACHE=/tmp/dws-go-path/pkg/mod go test ./test/scripts -run '^(TestSyncGiteeTag|TestGiteeReleaseWorkflowUsesImmutableTagsAndBoundedRetryBudget)' -count=1

Result: PASS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant