Chris Struble, Vertafore
Continuous Delivery may have come out of companies that were “born on the web”, but what if you are in a regulated industry with sensitive customer data, where every change to production must be approved by a review board? How can you design, deploy, and execute automated tests that will work in environments you don’t even have access to? How can you breach barriers to Continuous Delivery in a business context where the walls between development and operations are there for good reasons? Vertafore provides information solutions for insurance agencies, carriers, managing general agents, and state agencies. When our team was tasked to enable continuous delivery, we faced all of the above challenges. We overcame them using Jenkins,
Artifactory, and Chef to build a continuous delivery system with test gates for promoting product and test code from Dev through Staging to Production. Our continuous delivery system supports automatic promotion based on test results, or manual approval. Because of this flexibility, we were able to get adoption from product teams at different stages of continuous delivery thinking. It also provides a common way of deploying and testing that our developers, testers, and release engineers all use in the same way in each environment. The system has enabled our company to increase the size and frequency of releases with fewer issues during rollout.
This paper will cover the key patterns our team developed or discovered in our journey, which can help you in creating your own continuous delivery system even if you are using different tools.