[davewongillies]

Then you just follow the installation instructions on your iron behind your corporate firewall: https://hubot.github.com/docs/

My team controls our hubots on iron behind a firewall with hubot-control, which can also create hubots for you too: https://github.com/spajus/hubot-control

[Domenic_S]

Right, but then you need some kind of deployment adaptor to do something useful (like deploying apps) -- Heaven's the recommended one, but

> Heaven is a rails app that was designed to be hosted on heroku. https://github.com/atmos/heaven/blob/master/doc/installation...

Now we've got dependencies on node, npm, ruby, rails, heroku, some datastore, a queue for hubot, whatever your actual builder is (capistrano/chef/whatever) etc etc.

Right now I do all this with Jenkins+bash scripts. Inelegant and not as robust as I'd prefer, but so simple. I could just use a Jenkins adaptor for hubot, but then what's the point? I want locking environments, advanced permissions, and so forth.

I'm mostly complaining because I'm dying to implement chatops (mostly for slack-based deployments) but the information is really light, or the tools are too environment-specific, and I don't have people to bounce ideas/questions off of.