ci-automation/release.sh: Skip bucket copy on failure until it works #3481
Conversation
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
We got a DNS resolution problem due to UDP packets not going to the configured server. For now try the host network (and otherwise maybe a custom DNS server?). But in any case we should not block the release on that and continue. Signed-off-by: Kai Lueke <[email protected]>
sayanchowdhury
approved these changes
Nov 12, 2025
pothos
added a commit
that referenced
this pull request
Nov 12, 2025
ci-automation/release.sh: Skip bucket copy on failure until it works
pothos
added a commit
that referenced
this pull request
Nov 12, 2025
ci-automation/release.sh: Skip bucket copy on failure until it works
pothos
added a commit
that referenced
this pull request
Nov 12, 2025
ci-automation/release.sh: Skip bucket copy on failure until it works
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We got a DNS resolution problem due to UDP packets not going to the configured server. For now try the host network (and otherwise maybe a custom DNS server?).
But in any case we should not block the release on that and continue.
How to use
same as previous PR
Testing done
none