How we made QA’s life’s easier by providing builds conversing with a slack-bot
summary
Company builds a Slack bot called Bugs Bunny that triggers per-client iOS builds via Fastlane + Jenkins + Slack, runs in Docker and exposes Jenkins with ngrok, and queues requests so QA can launch builds without engineers. Per-ticket human work drops from roughly 30–60 minutes to 0–2 minutes for kickoff; CI build time stays ~12 minutes. Code signing and provisioning are automated with Fastlane (stored tokens/certificates), cutting manual errors and enabling on-demand white‑label deployments.
AI-written summary · about
chapters (13)
- 0:00Introduction and background
- 2:39Problems with manual builds
- 5:56Introducing Bugs Bunny bot
- 7:21Demo of Bugs Bunny in action
- 11:51Results and benefits achieved
- 13:02Fixing human mistakes
- 14:46Code signing improvements
- 16:15How the system works
- 18:43Current status and pride
- 19:03Future improvements planned
- 21:16Evolving the architecture
- 23:48Key takeaways and lessons
- 26:19Open-sourcing the solution
related talks
28mHow we do developer productivity at Slack
54mGetting out of quicksand, with DevOps!
39mOur journey to automated releases
46mAutomatic Deployment of iOS and/or Android Apps
37mWait, don’t click "Fix Issue"!
59mCI Best Practices for iOS & macOS App Development
44mSupercharging Your Mobile App Release with Fastlane
46mAutomating with fastlane Tips, Tricks, and Best Practices