Book Image

Jenkins Administrator's Guide

By : Calvin Sangbin Park, Lalit Adithya, Sam Gleske
Book Image

Jenkins Administrator's Guide

By: Calvin Sangbin Park, Lalit Adithya, Sam Gleske

Overview of this book

Jenkins is a renowned name among build and release CI/CD DevOps engineers because of its usefulness in automating builds, releases, and even operations. Despite its capabilities and popularity, it's not easy to scale Jenkins in a production environment. Jenkins Administrator's Guide will not only teach you how to set up a production-grade Jenkins instance from scratch, but also cover management and scaling strategies. This book will guide you through the steps for setting up a Jenkins instance on AWS and inside a corporate firewall, while discussing design choices and configuration options, such as TLS termination points and security policies. You’ll create CI/CD pipelines that are triggered through GitHub pull request events, and also understand the various Jenkinsfile syntax types to help you develop a build and release process unique to your requirements. For readers who are new to Amazon Web Services, the book has a dedicated chapter on AWS with screenshots. You’ll also get to grips with Jenkins Configuration as Code, disaster recovery, upgrading plans, removing bottlenecks, and more to help you manage and scale your Jenkins instance. By the end of this book, you’ll not only have a production-grade Jenkins instance with CI/CD pipelines in place, but also knowledge of best practices by industry experts.
Table of Contents (13 chapters)
12
Index

GitOps-Driven CD Pipeline with Docker Hub and More Jenkinsfile Features

The chapter title is quite a mouthful. Let's unpack it to understand what we'll learn in this chapter.

We will create a postmerge continuous delivery (CD) pipeline that is triggered when a pull request (PR) is merged. The crux of it is the same as the premerge CI pipeline from Chapter 3, GitOps-Driven CI Pipeline with GitHub – listen for an event from GitHub and build accordingly.

Unlike the premerge pipeline, which was entirely self-contained, the postmerge pipeline will interact with external systems to resemble a pipeline for a real product more closely. It will generate a tag based on the list of current tags in the Git repository, build a Docker image as an artifact, log in to Docker Hub (the primary Docker registry at https://hub.docker.com), push the image to Docker Hub, and then push the tag back to GitHub.

In implementing the tasks, we will use additional features of a...