The dos, the don’ts, the checklist: “Continuous Delivery is true agility”
What are the dos and don’ts when going down the Continuous Delivery path? What are the most common obstacles that teams will hit when moving towards CD? JAXenter editor Gabriela Motroc talked with Tommy Tynjä, Senior Software Engineer and Continuous Delivery Consultant at Diabol at JAX DevOps 2018 about all this and more.
Before you go down the Continuous Delivery road, you need to know the dos and don’ts, the obstacles and, more importantly, the things you need to focus on, namely writing quality software.
We talked with Tommy Tynjä, Senior Software Engineer and Continuous Delivery Consultant at Diabol at JAX DevOps 2018 about the difference between Continuous Delivery and DevOps, the ultimate Continuous Delivery checklist and the most popular tool for CI and CD today: Jenkins.
Tommy Tynjä is Senior Software Engineer and Continuous Delivery Consultant at Diabol. An advocate of open source software, Continuous Delivery, test driven development, automation and tools that boost developer productivity and get software shipped faster. Specializing in systems running on the Java platform. Has been contributing to various open source projects over the years, such as Arquillian and Apache TomEE. Currently maintainer of the Jenkins Delivery Pipeline plugin. Co-founder of the Continuous Delivery Stockholm meetup group.
If you want to hear more about Continuous Delivery and its pitfalls, check out this video interview.
Also, if you want to learn more about what makes achieving CD so difficult, check out this article.
It takes time to remove manual steps and shift toward automation, and you really need to be able to analyze your processes across all your teams to identify the bottlenecks and understand those changes that will make the most difference.