Jenkins has been known as a fairly inconvenient tool for deployment and management. This is due to the level of customization required for the deployment of a given piece of software. That fact in combination with the lack of methods to programmatically configure Jenkins has created a barrier to success that we’ll break down in this series. We’ll simplify the Jenkins deployment pattern in order to achieve CI system deployment repeatability and a reduction in CI infrastructure management overhead on top of deterministic continuous integration pipelines.