can't help you right now.
profitably-janky opened this issue · comments
I have janky and hubot deployed to heroku with hipchat. I am sure I must have the configs incorrect, but right now:
- Hubot shows up in hipchat
- "ci - show usage" shows up in hipchat as an options when I try
hubot help
in hipchat - when I try
hubot ci?
I get "can't help you right now."
Janky heroku config (abridged):
JANKY_BASE_URL: http://profitably-janky.herokuapp.com/
JANKY_BUILDER_DEFAULT: http://janky:[redacted]@jenkins.activecell.com/
JANKY_CHAT: hipchat
JANKY_CHAT_DEFAULT_ROOM: 26374
JANKY_CHAT_HIPCHAT_TOKEN: [redacted]
JANKY_CONFIG_DIR: /app/config
JANKY_GITHUB_HOOK_SECRET: secret
JANKY_GITHUB_PASSWORD: [redacted]
JANKY_GITHUB_USER: profitably-janky
JANKY_HUBOT_PASSWORD: hubot
JANKY_HUBOT_USER: hubot.mcbotson@profitably.com
Hubot heroku config:
HEROKU_URL => http://profitably-hubot.herokuapp.com
HUBOT_HIPCHAT_JID => 12111_129575@chat.hipchat.com
HUBOT_HIPCHAT_NAME => Hubot McBotson
HUBOT_HIPCHAT_PASSWORD => [redacted]
HUBOT_JANKY_URL => http://12111_129575:[redacted]@profitably-janky.herokuapp.com/_hubot
I'm sure it's something simple I'm missing here. Any thoughts? Thanks so much!
+1 on this. (It's not a bot that logged the issue!) We're having trouble getting connected. If someone could help us sort this out, I would be happy to fork and update the docs for anyone else running into this issue.
Anything in heroku logs
?
Heroku logs were just showing 401s. It was simple, as I suspected. The JANKY_HUBOT_USER needs to be XMPP/Jabber username if you're using hipchat. I will hit you with a pull request with a brief update to the README that might help other hipchat users if you think it's useful.