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.
|Field||Original Value||New Value|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Remote Link||This issue links to "PR 3718 (Web Link)" [ 22010 ]|
|Status||In Progress [ 3 ]||In Review [ 10005 ]|
|Status||In Review [ 10005 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|