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

Administrator versus non-administrator

There are several key concepts in understanding the Jenkins security model.

The first concept is administrator versus non-administrator. Jenkins security is structured around approving or denying pipeline codes and method signatures, and the administrators are the only users who can approve or deny them.

A user is an administrator if the Overall / Administrator box is checked on the Global Security page:

Figure 11.1 – admin user is an administrator because it has Overall/Administrator permission

In Chapter 3, GitOps-Driven CI Pipeline with GitHub, we have created project admin users – adder-admin and subtractor-admin. They are named *-admin and have all the permissions for their respective folders, but they do not have the Overall / Administrator permission, so they're not administrators. In our setup, admin is the only administrator user, and therefore only the admin user...