How does CloudBees deliver software continuously, with high quality? This is the story of how we changed from thinking of quality in the last phases of the SDLC, to having quality baked into our products from the design phase. It's also about our journey from releasing twice a year to releasing on a monthly basis through the power of CloudBees Jenkins Enterprise. Finally, how through all of this we have improved the quality of our products. Prevention vs detection is the key to our success.
We will touch base on some CloudBees best practices such as:
- Testing kick-off and quality bars: Acceptance criteria, test automation, exploratory testing, non-functional testing (usability, performance, security), dependencies and integrations. Quality is much more than just testing.
- Test automation at CloudBees: What are the tests that run on a plugin/core change basis before we merge our changes?
- Delivery process: How CloudBees leverages the power of CloudBees Jenkins Enterprise to cope with the new, faster release pace and portfolio growth, as well as our release process, including staging and promotion.
- Rollout plan: Dogfooding at CloudBees, feature flags, experimental update centers. We are customer-centric and we want to make sure that if an issue arises, we impact the least number of customers possible.
- Metrics: In order to know if you are getting better over time, you need to constantly measure quality. We will show what and how we measure.
