Creating Safe Environments that Inspire Innovation
summary
BlackBerry shifts from one brittle QA environment that cost $500k and six months to clone to a setup that can spin up four environments in minutes at negligible cost, using git, Jenkins, Chef, Selenium, Sonar, Fortify and SoapUI in a push‑button cloud pipeline. QA deployments drop from days to daily automated builds (9:00am), starting on a small test app then a new project, driven by volunteers given 20% time and embedded Ops change agents, and the automation removes recurring fires.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:03The decision to spin up a new environment
- 2:57What makes an environment safe
- 5:54What is BlackBerry
- 8:47How we tackled it
- 9:10The catalyst for us
- 12:09Our journey to DevOps
- 14:02Our basic DevOps stack
- 14:46Deploy our critical success factors
- 17:54Success challenges
- 21:31Automation
- 26:28Evangelists
related talks
46mMaking Security Agile
30mQA in DevOps: Transformation thru Automation via Jenkins
53mTransforming testing methodologies: From manual to robust strategies
44mAchieving Excellence in a Startup without a Dedicated QA
23mShipping Quality Software in Hostile Environments
32mBuilding Continuous Integration and Feedback
55mContinuously Delivering Continuous Delivery
32mHow to transform in a place where everyone says "cannot be done"?