Joep is a Build Master at TOPdesk with a keen interest in delivering quality software continuously. He loves playing around with Jenkins Pipelines, Selenium, Docker and keeps in touch with his inner developer by educating his colleagues on testable Java code.
Developers create software in a Development and Test environment. They then throw it over the wall to Ops who have to put it on Acceptance and Production. This classical DTAP street may involve many manual steps, typically involving the part where the software is thrown over the wall.
But there is a way to streamline this process! Drill a hole in the wall and feed a Pipeline through. Make this Software Delivery Pipeline bigger and bigger and the wall may crumble down.
Let me show you some Pipelines and how they got Development and Operations working more closely together in their combined goal of getting quality code delivered continuously.
Did you know that an average Jenkins installation has around 100 plugins installed to build and deploy software? And more and more plugins are added every day? Together with the new features in the weekly releases, Jenkins attempts to stay current in a competitive Continuous Integration and Continuous Deployment tooling landscape.
The downside of all these possibilities is that it is hard to wrap your head around what is possible with Jenkins and what are best practices.
At a rate of 1 tip per minute I'll take you through some core and advanced features to successfully unleash the full potential of Jenkins in your CD process. Tips are applicable to both Jenkins novices and pros. So even if you know the differences between Declarative and Scripted Pipelines, you'll probably pick up some new tricks.