Jenkins is one of the most popular tools for Continuous Integration and Continuous Delivery today. 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 his many years of experiences from working with Jenkins for Continuous Delivery. Watch the full session to learn about pros and cons of different approaches but also how Jenkins compares to its competitors, where it shines, and where it leaves room for improvement.