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

Storage concerns

The following is very important:

Everything in Jenkins is a flat file on the controller.

Everything in Jenkins is a flat file on the controller.

Everything in Jenkins is a flat file on the controller.

The controller's storage is extremely important to the performance of Jenkins and the backup/restore process. Jenkins doesn't use a database as a backend. Instead, it uses directories and files to store and look up everything. On a mid-sized Jenkins installation with a hundred pipelines, the controller runs dozens of builds concurrently and keeps track of tens of thousands of build history. This results in hundreds of open files and hundreds of thousands of small files stored for history tracking. The performance of Jenkins is dictated almost entirely by the storage's input/output operations per second (IOPS). The storage medium determines how far you can scale the Jenkins instance in terms of both its performance and maintenance...