Open flabrie opened 3 weeks ago
Can you provide your Slack configuration and how you're sending messages through Jenkins?
I suspect its your slack configuration and not a proxy issue.
Here you'll find the Slack configuration:
I get the failure using the Test Connection button. And here it's a Jenkins job usage example:
Nothing is set in the Advanced settings.
Does getting updates for plugins work when you click check for updates? (to verify proxy configuration is right)
The code path you are going down should be:
From reading through I can't see anywhere a proxy is missed and I'd expect more people to have issues if so.
Does getting updates for plugins work when you click check for updates? (to verify proxy configuration is right)
Yes, it works. All other plugins requiring to reach an external server uses the proxy successfully. Here is the HTTP proxy configuration:
The code path you are going down should be:
From reading through I can't see anywhere a proxy is missed and I'd expect more people to have issues if so.
Yes, I see. Can you tell me what's the hostname the plugin try to reach? Or is it an IP address? Because only *.slack.com
domain is whitelisted for this plugin on our proxy.
for your configuration its coemobile.slack.com
All looks configured right
Jenkins and plugins versions report
Environment
```Red hat Enterprise Linux 7 Jenkins 2.461 Slack Notification Plugin 722.vd07f1ea_7ff40 ```We use the Slack Notification Plugin on several Jenkins service running on different systems (macOS and Linux), using the same configuration. It works without issue on all Jenkins, except the one RHEL 7 server behind an HTTP proxy.
Jenkins is correctly setup with the proxy settings: all other plugins use it without issue.
The
*.slack.com
domain name it correctly whitelisted by the proxy. We can even test is from the server command line using a curl command line:But through Jenkins, we get a Failure message when the Test Connection button is used on the settings, and no notification are received. And we can find a 404 error in Jenkins' log:
And as mentioned above, the HTTP proxy settings are correctly set in Jenkins.
What Operating System are you using (both controller, and any agents involved in the problem)?
Red Hat Enterprise Linux 7
Reproduction steps
Expected Results
Expecting Slack Notification Plugin to use Jenkins HTTP Proxy Configuration to send messages.
Actual Results
Slack Notification Plugin doesn't seem to reach Slack Services
Anything else?
No response
Are you interested in contributing a fix?
No response