[JIRA] (JENKINS-54459) Avoid Angry Jenkins when check now on Plugin Manager

2018-11-20 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated  JENKINS-54459  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54459  
 
 
  Avoid Angry Jenkins when check now on Plugin Manager   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
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-54459) Avoid Angry Jenkins when check now on Plugin Manager

2018-11-06 Thread manuelramonleonjime...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramon Leon commented on  JENKINS-54459  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Avoid Angry Jenkins when check now on Plugin Manager   
 

  
 
 
 
 

 
 Link to the pull request: https://github.com/jenkinsci/jenkins/pull/3718  
 

  
 
 
 
 

 
 
 

 
 
 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-54459) Avoid Angry Jenkins when check now on Plugin Manager

2018-11-06 Thread manuelramonleonjime...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramon Leon updated  JENKINS-54459  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54459  
 
 
  Avoid Angry Jenkins when check now on Plugin Manager   
 

  
 
 
 
 

 
Change By: 
 Ramon Leon  
 
 
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-54459) Avoid Angry Jenkins when check now on Plugin Manager

2018-11-05 Thread manuelramonleonjime...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramon Leon started work on  JENKINS-54459  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Ramon Leon  
 
 
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-54459) Avoid Angry Jenkins when check now on Plugin Manager

2018-11-05 Thread manuelramonleonjime...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramon Leon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54459  
 
 
  Avoid Angry Jenkins when check now on Plugin Manager   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Ramon Leon  
 
 
Components: 
 core  
 
 
Created: 
 2018-11-05 12:38  
 
 
Labels: 
 user-experience  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ramon Leon  
 

  
 
 
 
 

 
 Avoid showing the angry Jenkins with all the stack trace when a problem happens checking the update sites. It's common (unfortunately) that update site returns a 502 error code, so it's interesting to avoid showing the Angry Jenkins and all the stack trace. Also a mechanism to retry several times before raising an error will be helpful.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment