-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use slack notification #20
Comments
Seems like a bug. Will check it out. |
hi @lyrixx Just released the v0.1.2 and we now have a better error message for slack. Thanks for this. |
OK, I will try this ASAP ;) |
So I tested it, and now in the log I got: time="2014-11-14T09:49:22Z" level="info" msg="Unable to notify slack: No hooks" Do you have an idea? I have create a token on https://api.slack.com/ |
Might be possible that you configured it wrong? I got this error when I had the wrong token. Slack's a bit tricky to get running as the return message from their API is pretty vague. My bet is it can be the token, or some other variable that's part of the hook URL. |
The
Basically what the slack notifier does is send a payload to this url:
|
I don't understand why it did not work. I try to curl it manually: (I copied it from https://api.slack.com/)
|
I tried it with ours and it seems to work. It might be the token.
The last time I got a No hooks error was when I got the token wrong. |
I open an issue in slack
But I don't understand someting with your URL. I'm not able to find the documentation about it, and It don't understand why you don't use the "regular" API documented there https://api.slack.com/methods/chat.postMessage ? |
hmm, I understand What I did wrong. I will submit a (doc) PR to your repository to help others user (after lunch) ;) |
Voila, I just open a PR: #23 |
Cool. Thanks. Merged. :) |
Wahoo, So fast ;) I hope It will help new comers ;) |
I'm unable to set-up slack notifications.
I can do anything, the log output is always
(I try with a wrong token).
So it's not easy to debug...
The text was updated successfully, but these errors were encountered: