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

Mon, 13 Apr 2015 23:36:13 -0700

Daniel Beck commented on Bug JENKINS-27917

And my point is, how do you expect a user to know the issue is their proxy setup when you have a vague, misspelled error message that doesn't in any way indicate this?

I read 're-opening' to mean reading and reopening this specific issue, which contains the solution in the comments.

Please change the error message to something along the lines of, "Jenkins received an unexpected response. Please check your proxy/network configuration."

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

Reply via email to