Feature request: More logging in case of connection failures.

[andrewspiers]

I am trying to use version 2.2 of the Slack Plugin, with Jenkins 2.46.3.

The connection test fails. In the Jenkins logs, I can see that slack is returning a 404, and the whole response is also sent.

I cannot see exactly which URL the plugin is calling.
I cannot see the request headers that are sent.

Would it be possible to log these in the case of a connection error?

[prachikhadke]

I am also hitting this issue. Might be similar to #323 except I don't get No hooks in the response. Instead I get Slack's standard 404 page (i.e. https://slack.com/404).

Jun 19, 2017 6:23:13 AM jenkins.plugins.slack.StandardSlackService publish
WARNING: Response Code: 404
Jun 19, 2017 6:25:27 AM jenkins.plugins.slack.StandardSlackService publish
WARNING: Slack post may have failed. Response:  

where the response is the 404 html page contents.

[EDIT]: I fixed the 404 by updating the Base Server URL: I needed to specify the Jenkins home page. See https://github.com/jenkinsci/slack-plugin/blob/master/README.md. But now that's giving me 504. Need to figure out why.

[jstoja]

Here I get a 302, no idea what's wrong...

[andrewspiers]

I meant to add, this plugin can actually log what it sends. I couldn't see these log messages in jenkins' logs of standard out. I did manage to get the logs viewable by configuring logging specifically for this plugin, from within Jenkins.

[timja]

Logging has been improved