Continuous delivery with Jenkins: The good, the bad and the ugly

Jenkins is one of the most popular tools for Continuous Integration and Continuous Delivery today and it’s easy to set up and get started with. But what are the best practices for building delivery pipelines with Jenkins? Should you use the traditional build jobs or opt for the new Jenkins pipelines? What options are there for, e.g. visualization or infrastructure as code support? How to structure my shared libraries so that they’re easy to maintain?

In this talk, Tommy Tynjä, Senior Software Engineer and Continuous Delivery Consultant at Diabol, shares the lessons learned from his long experience working with Jenkins for Continuous Delivery. Watch the full session to learn about the pros and cons of different approaches but also where Jenkins stands against its competitors, where it shines, and where it leaves room for improvement.

kqkehqpew

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.

wihepq