hubot-hipchat

Quickstart: Hubot for HipChat on Heroku

This is a HipChat-specific version of the more general instructions in the Hubot wiki.

1. Create a new HipChat account for your bot to use. Stay signed in to the account - we'll need to access its account settings later. We'll assume the bot's name is "Hubot Botson" in these instructions.

2. Download the latest Hubot archive from https://github.com/github/hubot/downloads

3. Extract it

4. Edit hubot/packages.json and add hubot-hipchat to the dependencies section. It should look something like this:

    "dependencies": {
      "hubot-hipchat": ">= 1.0.3",
      "hubot": ">= 2.0.1",
      ...
    }
   

5. Edit Procfile and change it to use the hipchat adapter. If your bot's first name is not "Hubot" you'll want to edit the name here as well:

    app: bin/hubot -a hipchat -n Hubot
   

6. Turn your hubot directory into a git repository:

    % cd hubot/
    % git init
    % git add .
    % git commit -m "Initial commit"
   

7. Install the Heroku command line tools if you don't have them installed yet.

8. Create a new Heroku application and (optionally) rename it:

    % heroku create --stack cedar
    % heroku rename our-company-hubot
   

9. Configure it:

   Set the JID to the "Jabber ID" shown on your bot's XMPP/Jabber account settings:

    % heroku config:add HUBOT_HIPCHAT_JID="..."
   

   Set the name to match the "Room nickname" value on the same page:

    % heroku config:add HUBOT_HIPCHAT_NAME="..."
   

   Set the password to the password chosen when you created the bot's account.

    % heroku config:add HUBOT_HIPCHAT_PASSWORD="..."
   

10. Deploy and start the bot:

     % git push heroku master
     % heroku ps:scale app=1
    

11. You should see the bot join all rooms it has access to. If not, check the output of heroku logs. You can also use heroku config to check the config vars and heroku restart to restart the bot. heroku ps will show you its current process state.

12. Assuming your bot's name is "Hubot", the bot will respond to commands like "@hubot help". It will also respond in 1-1 chat.

13. To configure the commands the bot responds to, you'll need to edit the hubot-scripts.json file (valid script names here) or add scripts to the scripts/ directory.

14. To deploy an updated version of the bot, simply commit your changes and run git push heroku master again.

Bonus: Add a notification hook to Heroku so a notification is sent to a room whenever the bot is updated: https://www.hipchat.com/help/page/heroku-integration

Adapter configuration

This adapter uses the following environment variables:

HUBOT_HIPCHAT_JID

This is your bot's Jabber ID which can be found in your XMPP/Jabber account settings. It will look something like [email protected]

HUBOT_HIPCHAT_NAME

This is the full name exactly as you see it on the HipChat account for your bot. For example, "Hubot Botson". It must match the name set on the HipChat account or it will be unable to join rooms.

HUBOT_HIPCHAT_PASSWORD

This is the password for your bot's HipChat account.

HUBOT_HIPCHAT_ROOMS

Optional. This is a comma separated list of room JIDs that you want your bot to join. You can leave this blank or set it to "@All" to have your bot join every room. Room JIDs look like "[email protected]" and can be found in the XMPP/Jabber account settings - just add "@conf.hipchat.com" to the end of the room's "XMPP/Jabber Name".

HUBOT_HIPCHAT_DEBUG

Optional. Set to true to enable some additional debug logging.

HUBOT_HIPCHAT_HOST

Optional. Use to force the host to open the XMPP connection to.

Running locally

To run locally on OSX or Linux you'll need to set the required environment variables and run the bin/hubot script. An example script to run the bot might look like:

#!/bin/bash

export HUBOT_HIPCHAT_JID="..."
export HUBOT_HIPCHAT_NAME="..."
export HUBOT_HIPCHAT_PASSWORD="..."

~/hubot/bin/hubot -a hipchat -n Hubot

OSX note

This adapter requires node-stringprep which in turn, requires icu-config to be available in the path. You'll need to install icu4c, which, conveniently, homebrew can take care of for you:

% brew install icu4c

But brew will not link any of the utilities, you'll have to do that by hand (in particular icu-config which is needed for node-stringprep to build correctly (it'll just appear like a broken package otherwise which will be really disturbing)). You can link it with brew using brew link icu4c.