Optimizing Delivery with SlackOps
summary
Replit builds a SlackOps bot called Cyclops that queues builds, enforces multi-approval gating for every author in a batched release, and adds bi-directional sync with the CD system so Slack and the deploy platform never disagree. The flow handles 35 deployments on busy days and replaces slash commands with interactive buttons, 30‑minute reminder bumps, rollback/abort actions, and terraform plan approvals. Rollout starts with the website then infrastructure, and incremental use shows the system works and scales.
AI-written summary · about
chapters (13)
- 0:00Introduction to SlackOps
- 1:11Why optimize continuous delivery
- 3:17Moving off Heroku ChatOps
- 5:03Why Slack for ChatOps
- 6:27Incremental improvements in flow
- 8:34Bi-directional sync and rollbacks
- 10:00Real-world SlackOps examples
- 12:52Extending SlackOps beyond code
- 14:15Balancing information and usability
- 15:36Automating tedious deployment tasks
- 16:18Future optimizations and challenges
- 17:42Onboarding and internal UX
- 18:26Key takeaways and summary
related talks
31mWhen Failure Is Not an Option: From Fully Manual to Slack-based Deployments at ITIVITI
01h 02mProductivity Bots
42mEmbrace chatops, stop installing deployment software
28mHow we do developer productivity at Slack
34mDeploy, Release, CI/CD, Oh My! DevOps for the Rest of Us
43mContinuous Deployment: The GitOps, The Pipelines, and The Ugly
51mChatOps, or How to Do DevOps from Slack
25mDevOps Handbook Experiments in Accelerating Delivery