-
Notifications
You must be signed in to change notification settings - Fork 736
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
[JENKINS-45142] Retry connections after getting SocketTimeoutException #359
[JENKINS-45142] Retry connections after getting SocketTimeoutException #359
Conversation
BTW I get a ton of failures/errors running tests in this component, which I doubt are caused by my changes here. |
This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation. |
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.
works for me 🐝
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.
I wonder if @rtlyer was being hit by the azure NAT router timeout though
In my github plugins i just do retryable executions from Function and that's all. |
@reviewbybees done |
Yes it is possible to work around from the caller side, but to limit the fix to the known case where a retry is definitely sensible, it would be necessary to inspect |
JENKINS-45142
@reviewbybees