Working with sharp tools — continuous integration and deployment as a way to reduce friction
summary
A sales‑force app used in 22 countries and 28 languages for a 117000‑employee company proves continuous integration and deployment cuts friction: a SOAP API returns 1MB XML endpoints that take 10 to 12 seconds to respond, so a Bitrise build pipeline plus distribution via hockey and github puts daily builds into hands of management and customers, surfacing performance and crash data via slack and Trello and using poeira tor for localization; the pipeline works and the app ships with fewer surprises.
AI-written summary · about
chapters (16)
- 0:00Intro
- 7:45Requirements and specifications
- 14:35Build pipeline
- 16:26App vs IT project
- 18:22App focus
- 20:22Why
- 24:27Direction
- 27:03Slack
- 31:51Trello
- 33:51Pipeline
- 35:33Voyager
- 37:45Coffee
- 38:54Limitations
- 40:26Key takeaways
- 42:08Questions
- 49:38Crash reports
related talks
11mWorking with sharp tools - A case study of Continuous deployment
01h 01mA team's transition to Continuous Delivery
46mThe Software Factory
34mEnabling a Continuous Deployment Mindset
28mDOES14 - Bill Donaldson and Aimee Bechtle - The MITRE Corp
49mThe road to continuous deployment: a case study
47mContinuous Delivery Warstories
33mcontinuous happiness as a service