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

Let's Encrypt

Let's Encrypt is a non-profit certificate authority that provides X.509 certificates for TLS communication at no charge.

When we request a certificate from Let's Encrypt, we need to provide proof of ownership for our domain. This can be done in one of two ways. We can either manually add a TXT record to our DNS provider or we can allow Certbot to automatically create a TXT record for us in Route 53. The latter method will only work if we are managing our DNS records in Amazon Route 53. The former method can be used for any DNS provider.

Manual verification

When we start the Certbot Docker container with the manual verification flag, we will see the following block of text:

- - - - - - - - - - - - - - - - - - - - - - - - - 
Please deploy a DNS TXT record under the name
_acme-challenge.jenkins-firewalled.lvin.ca with the following value: 
kLmhtIfqI5PZFuk-lXna13Z4_oIYDmaJoPd6RaFgwqQ 
Before continuing, verify...