ChatOps at GitHub - Jesse Newland
Channel:Rubyfuza · Length:36:27 · Published:2013-03-16 · Views:31576
Summary
Jesse Newland describes how GitHub uses Hubot, its chat bot, to run operations such as deployment, monitoring, graphing and provisioning from chat rooms. He explains how this improves shared awareness and remote work culture.
Why HN recommends it
The go-to reference for ChatOps, recommended for the idea of chat as a shared command line where teammates learn by watching.
There's a pretty good talk on "chatops" by the guys at GitHub[0]. — HN, 2015
Testing, debugging & developer tools · Cloud, DevOps & reliability
Subtitles (excerpt)
hey everyone uh my name is Jesse newand and I do ops at GitHub the sticker and t-shirt company that also happens to have a little bit of gith Hosting on the side I'm uh Jay nuland on most of the internets and today I'm going to be talking about chat Ops at GitHub so what is chat Ops chatops is what we've been calling the pattern of automating common operational tasks with hubot hubot is our campfire IRC um jabber several different transports but it's a it's essentially a chatbot it's like egg drop way back in the day um it's very simple pattern for or interacting with a robot in your chat room so hubot began is a very very simple campfire bot you can do things like math and return funny images but it doesn't do just that anymore it's evolved into something completely different cubot has evolved into essentially the primary control surface for our entire infrastructure so explaining how that works and why that's important is is kind of hard just from the outside in so I'll start with an example so let's say that vent on our systems team has made some awesome patches to get and he wants to roll those out to our infrastructure and in a controlled fashion he thinks it's ready to go but he wants
On Hacker News
There's a pretty good talk on "chatops" by the guys at GitHub[0]. Basically, it provides a dialog around a "shared command-line" where developers from learn from each other by simply watching chat. I think it's more beneficial to distributed companies. However, my question for those using chatops is basically how do you keep the repository for the bot "tame"? It needs access to _everything_ if yo… — jzelinskie, 2015-12
Absolutely. As I mentioned, we have 150+ rooms that we chill in, and most of our day-to-day work practices are tied into chat. Mention someone's name in a room they're not present in and we send push notifications to their phone and desktop- works great to pull people in as needed, without needing to distract them with the noise of being in the room 24/7. Our ops team is particularly in deep with… — holman, 2013-11
Github is well know for doing chatops for everything . In fact, I think they may have invented the term. Here's a relevant talk from 2013: [VIDEO] — sciurus, 2021-01
3. Never grand direct SSH to access the the staging/production environment. Automate the build and deployment environment on a system that developers don't have direct access. Instead of pushing changes, the bot pulls a specified release branch, builds, tests, and deploys the code. All without human interaction. If malicious code were somehow introduced from a developer's environment, it would be… — EvanPlaice, 2016-02
The DevOps approach: Just write a Slack plugin for all those things, if they don't already exist (they totally do tho). /s In all seriousness. Communication IS the baseline requirement for the super-app you speak of. The next requirement is making the platform talk to any data source. Slack does both of these things surprisingly well. Check this out: [VIDEO] — EvanPlaice, 2016-01
Related videos
- OpenFlow @ Google - Urs Hoelzle, Google · Open Networking Summit · 47:18
- RailsConf 2014 - All the Little Things by Sandi Metz · Confreaks · 38:47
- "Testing Distributed Systems w/ Deterministic Simulation" by Will Wilson · Strange Loop Conference · 40:20
- 🚀 TDD, Where Did It All Go Wrong (Ian Cooper) · DevTernity Conference · 1:03:55
- Bret Victor - Inventing on Principle · Rui Oliveira · 54:20
- Velocity NY 2013: Richard Cook, "Resilience In Complex Adaptive Systems" · O'Reilly · 19:09
- Solving Problems the Clojure Way - Rafal Dittwald · Clojure/north · 1:02:26
- Debugging Under Fire: Keep your Head when Systems have Lost their Mind • Bryan Cantrill • GOTO 2017 · GOTO Conferences · 52:34
- "Performance Matters" by Emery Berger · Strange Loop Conference · 42:15
- AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401) · Amazon Web Services · 59:56
- A Tour of the Acme Editor · Russ Cox · 23:16
- Tech Talk: Linus Torvalds on git · Google · 1:10:15
- "How NOT to Measure Latency" by Gil Tene · Strange Loop Conference · 42:59
- Ruby Conf 12 - Boundaries by Gary Bernhardt · Confreaks · 45:55
- Using Python to Code by Voice · Next Day Video · 28:17
- How to Do 90% of What Plugins Do (With Just Vim) · thoughtbot · 1:14:02