Testing a single piece of software is a proven practice - there's an extended ecosystem to ensure that a piece of software does what it's supposed to do in its sandbox. Testing a set of software components - a distribution - that are supposed to work together, and can be configured in a myriad of different ways, is something else. What every team wants when hitting their project's release button is a stable release that's been tested for all possible permutations and that doesn't break their setup. Enter: Distributed Continuous Integration (DCI). The more users, partners, and customers there are, the more configurations are tested, and the stronger the product stability gets. In this session, you'll learn about the elements of DCI, and how it's been used to provide feedback for a project as complex as OpenStack. We'll also look at how partners and customers are using DCI for completely different architectures and deployment use cases.