Skip to content
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

Merged
merged 1 commit into from
Jun 29, 2017

Conversation

jglick
Copy link
Contributor

@jglick jglick commented Jun 28, 2017

JENKINS-45142

@reviewbybees

@jglick
Copy link
Contributor Author

jglick commented Jun 28, 2017

BTW I get a ton of failures/errors running tests in this component, which I doubt are caused by my changes here.

@ghost
Copy link

ghost commented Jun 28, 2017

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.

@stephenc
Copy link
Contributor

stephenc commented Jun 29, 2017

Copy link
Collaborator

@oleg-nenashev oleg-nenashev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

works for me 🐝

Copy link
Contributor

@stephenc stephenc left a 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

@KostyaSha
Copy link
Contributor

In my github plugins i just do retryable executions from Function and that's all.

@jglick
Copy link
Contributor Author

jglick commented Jun 29, 2017

@reviewbybees done

@kohsuke kohsuke merged commit 0f21eba into hub4j:master Jun 29, 2017
@jglick jglick deleted the SocketTimeoutException-JENKINS-45142 branch June 29, 2017 21:28
@jglick
Copy link
Contributor Author

jglick commented Jul 3, 2017

do retryable executions from Function

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 causes for instanceof SocketTimeoutException.

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.

5 participants