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

Approve assuming permission check

A method call for deleting a pipeline is dangerous yet necessary for managing Jenkins, so that the project admins can programmatically delete unused pipelines. What if there were a way to allow deleting only the pipelines that a user has the permissions to delete? That is where the Approve assuming permission check button comes in.

Feel free to skip this section

The button fills an important gap in Jenkins security; however, there are a few challenges in making the button useful. Getting this to work and understanding why it works requires an extensive understanding of the Jenkins security model. Even if you do get it to work, there are so few methods that implement this feature that it's not really useful. Given the steep learning curve and low utility, my practical recommendation is to use the global shared library wrappers from the previous section instead. Go ahead and follow along for fun (oh the things we do for fun...