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

Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, folder names, filenames, dummy URLs, and user input. Here is an example: “For example, builds for a pipeline that specifies agent { label 'ubuntu2004-agent' } would run only on ubuntu2004-agent, even if you didn’t label the agent with its own name.”

A block of code is set as follows:

$ ssh [email protected]
$ docker ps
CONTAINER ID   IMAGE   COMMAND  CREATED  STATUS  PORTS  NAMES

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

$ sudo usermod -aG docker $USER
$ exit
logout 

Screen text: Indicates words that you see onscreen. Here is an example: “Click Save and Finish to continue (we will change this soon), then click Start using Jenkins.”

Italics: Indicates an important word a phrase. Here is an example: “Most importantly, you are responsible for the restoration in the event of a disaster.”

Tips or important notes

Appear like this.