6 ms·

The Hubot workflow sounds interesting. It seems more and more DevOps prefer it. Has someone first hand experience with such Hubot usage? Do you prefer such com

by castell 11y ago

The Hubot workflow sounds interesting. It seems more and more DevOps prefer it. Has someone first hand experience with such Hubot usage? Do you prefer such commands or would you want to write more informal short sentences?

Rockslide 11y ago
There was also a talk titled "Chatops" about this specific thing if you want to learn more: https://www.youtube.com/watch?v=NST3u-GjjFw https://www.youtube.com/watch?v=NST3u-GjjFw
jon-wood 11y ago
I'm somewhat split. There's definite value in having a shared history of what people have done, but I prefer that to take the form of command line tools pushing status updates to Hipchat or whatever. You lose so much convineance by pretending Hipchat's chat box is a terminal, everything from command history to being able to quickly iterate over the contents of a file or set environment variables.
- glenngillen 11y ago
  One of the most compelling aspects of it for me isn't so much the shared history, but just visibility of what people have done. It's a really effective way of transferring knowledge of how things are done. You can easily drop into the room and watch play-by-play how a given task is done.
  - greggyb 11y ago
    If this is the goal, why not just have a script export the shell's history to a chat channel? To me, a wiki would be even better, because you could retroactively include expository comments along with the command history.
ktt 11y ago
Unfortunately most of the material on ChatOps currently covers only how to get Hubot to display cat pictures or other trivia [1]. Maybe it's because each company should create their own "chat API" but I'd also like to hear some real, inside "war stories". Does anyone knows what app does GitHub use for chats? Looks like a simple and elegant UI over Basecamp. [1]: http://hubot-script-catalog.herokuapp.com/ http://hubot-script-catalog.herokuapp.com/
- tehbeard 11y ago
  Going off Hubot's sourcecode, I'd guess campfire.
q3k 11y ago
Semi-off-topic, but I am genuinely scared by giving a chat bot full root access to your infrastructure. This just doesn't seem like a mature enough, AAA-enabled channel. Especially when there's a third party (HipChat/Slack/...) involved.

by castell 11y ago

Rockslide 11y ago

There was also a talk titled "Chatops" about this specific thing if you want to learn more: https://www.youtube.com/watch?v=NST3u-GjjFw https://www.youtube.com/watch?v=NST3u-GjjFw

jon-wood 11y ago

I'm somewhat split. There's definite value in having a shared history of what people have done, but I prefer that to take the form of command line tools pushing status updates to Hipchat or whatever. You lose so much convineance by pretending Hipchat's chat box is a terminal, everything from command history to being able to quickly iterate over the contents of a file or set environment variables.

glenngillen 11y ago
One of the most compelling aspects of it for me isn't so much the shared history, but just visibility of what people have done. It's a really effective way of transferring knowledge of how things are done. You can easily drop into the room and watch play-by-play how a given task is done.
- greggyb 11y ago
  If this is the goal, why not just have a script export the shell's history to a chat channel? To me, a wiki would be even better, because you could retroactively include expository comments along with the command history.

ktt 11y ago

Unfortunately most of the material on ChatOps currently covers only how to get Hubot to display cat pictures or other trivia [1]. Maybe it's because each company should create their own "chat API" but I'd also like to hear some real, inside "war stories". Does anyone knows what app does GitHub use for chats? Looks like a simple and elegant UI over Basecamp. [1]: http://hubot-script-catalog.herokuapp.com/ http://hubot-script-catalog.herokuapp.com/

tehbeard 11y ago
Going off Hubot's sourcecode, I'd guess campfire.

q3k 11y ago

Semi-off-topic, but I am genuinely scared by giving a chat bot full root access to your infrastructure. This just doesn't seem like a mature enough, AAA-enabled channel. Especially when there's a third party (HipChat/Slack/...) involved.