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.
Originally reported by 
mramonleon, imported from: Avoid Angry Jenkins when check now on Plugin Manager
- assignee: mramonleon
- status: Resolved
- priority: Minor
- component(s): core
- label(s): user-experience
- resolution: Fixed
- resolved: 2018-11-20T14:52:59+00:00
- votes: 0
- watchers: 1
- imported: 2025-11-24
Raw content of original issue
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.
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.
Originally reported by
mramonleon, imported from: Avoid Angry Jenkins when check now on Plugin Manager
Raw content of original issue