You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The settings were made with reference to the README.
but, when I run "Test Connection", I get the following error:
Custom slack app bot user -> OFF
WARNING j.p.slack.StandardSlackService#publish: Slack post may have failed. Response: null
WARNING j.p.slack.StandardSlackService#publish: Response Code: 404
Custom slack app bot user -> ON
WARNING j.p.slack.StandardSlackService#publish: Slack post may have failed. Response: {"ok":false,"error":"invalid_auth"}
WARNING j.p.slack.StandardSlackService#publish: Response Code: 200
Thanks! Jenkins CI approved but did not create a custom Slack bot.
I finally understood the meaning of the legacy, and when I made a custom Slack bot, I succeeded in "Test Connection".
I couldn't understand what the "legacy" was showing. So, I felt it would be better to explain the old version and the current setting method a little more clearly.
overview
The settings were made with reference to the README.
but, when I run "Test Connection", I get the following error:
Custom slack app bot user
-> OFFCustom slack app bot user
-> ONSettings
.jenkins/jenkins.plugins.slack.SlackNotifier.xml
env
Description
The situation did not change even after uninstalling and installing again.
Also, I checked the following issue and did not resolve it.
invalid_auth
from Slack #631The text was updated successfully, but these errors were encountered: