-
Notifications
You must be signed in to change notification settings - Fork 41
add retry for GH release creation #79
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.
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
Conversation
viren-nadkarni
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for following up on this, looks good to me!
| uses: nick-fields/retry@v3 | ||
| with: | ||
| max_attempts: 5 | ||
| retry_wait_seconds: 120 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could use a shorter wait and more retries to avoid keeping the CI worker blocked
|
FYI: There was one more fix necessary (adding |
|
FYI: One more fix was necessary (adding the |
Motivation
Last week we added a CI workflow to automatically sync and release this fork for us (see #78).
Unfortunately, one step is still not stable: The actual creation of the release on GitHub. While this is optional, it would be nice to have the release properly being shown in the UI.
The step fails with the following error:
The logs clearly show that the tag is pushed, but is not recognized by GitHub right afterwards.
This PR tries to address this issue by wrapping the release creation into a "retry" action.
Changes