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

Creating a premerge CI pipeline with GitHub PR hooks

Required plugins

GitHub Pull Request Builder

A static pipeline is nice, but what we really need is a premerge CI pipeline that is triggered when a PR is created or updated. GitHub triggers a premerge build when a PR is created or updated, Jenkins runs the build, and Jenkins reports the status back to the PR in GitHub:

Figure 3.16 – Premerge build workflow

There are two ways to do this. For the AWS controller, GitHub can push the trigger directly since GitHub can reach the controller over the internet:

Figure 3.17 – Network access rules among GitHub, AWS Jenkins, and firewalled Jenkins

The firewalled controller, on the other hand, cannot be reached from GitHub, therefore we need a different way to trigger the build.

GitHub personal access token

Let's start by creating a personal access token...