[JIRA] (JENKINS-51304) All evergreen-client calls should retry on connection failures.

2018-09-14 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy updated  JENKINS-51304  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51304  
 
 
  All evergreen-client calls should retry on connection failures.   
 

  
 
 
 
 

 
Change By: 
 R. Tyler Croy  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-51304) All evergreen-client calls should retry on connection failures.

2018-09-13 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy updated  JENKINS-51304  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51304  
 
 
  All evergreen-client calls should retry on connection failures.   
 

  
 
 
 
 

 
Change By: 
 R. Tyler Croy  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-51304) All evergreen-client calls should retry on connection failures.

2018-09-13 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy assigned an issue to R. Tyler Croy  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I believe this is redundant with this change to rely on socket.io as the default transport in the client  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-51304  
 
 
  All evergreen-client calls should retry on connection failures.   
 

  
 
 
 
 

 
Change By: 
 R. Tyler Croy  
 
 
Assignee: 
 Baptiste Mathus R. Tyler Croy  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-51304) All evergreen-client calls should retry on connection failures.

2018-09-13 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy started work on  JENKINS-51304  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 R. Tyler Croy  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-51304) All evergreen-client calls should retry on connection failures.

2018-05-14 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51304  
 
 
  All evergreen-client calls should retry on connection failures.   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 R. Tyler Croy  
 
 
Components: 
 essentials  
 
 
Created: 
 2018-05-14 16:06  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 R. Tyler Croy  
 

  
 
 
 
 

 
 Transport level errors (failed to connect, connection reset) should retry with some configurable exponential backoff. HTTP errors should not, unless it's 429.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA