[JIRA] [core] (JENKINS-27917) Stack Trace when Checking for Updates

[mark.nej...@trexcorporation.com (JIRA)]

Mark Nejman commented on JENKINS-27917 Stack Trace when Checking for Updates The problem here is that this requires an assumption such as 'all invalid JSON responses are due to no proxy being set up', something I doubt is reasonably accurate. There can be any number of reasons. (In fact, the redirect seems to be fairly braindead to me, as it'll break all kinds of tools not used interactively. It should at least set some HTTP error code in the response so automated tools know to fail.) Do you think it would it help to wrap the error in a more generic 'failed to parse JSON update center metadata', and maybe show an excerpt of the data? Yes, I understand, you don't want to write error messages that are guessing what the issue is. I do think your proposed error message would be clear though.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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.