Add retry logic for Docker build and push #1882
Merged
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.
The Docker build fetches packages from PyPI inside the container. Due to CDN propagation delays after a release, the build may fail if it hits a different CDN node than the one where the package was originally published.
This adds retry logic using
nick-fields/retry@v3with up to 5 attempts and a 10-minute timeout per attempt, matching the pattern used in https://github.com/adamtheturtle/doccmd/.Note
Introduces retry logic around the Docker image build/push in the release workflow to handle PyPI CDN propagation races.
docker/build-push-action@v6withnick-fields/retry@v3runningdocker buildx build --pushforlinux/amd64, linux/arm64, tagging${{ steps.calver.outputs.release }}andlatest, and passingVWS_CLI_VERSIONas a build argmax_attempts: 5,timeout_minutes: 10; add comments explaining the PyPI race conditionWritten by Cursor Bugbot for commit a7f74ce. This will update automatically on new commits. Configure here.