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

Converting agent configuration to JCasC

Similar to the controller configuration, let's identify all the changes we've made for agent configuration, then find out how to apply the same changes using JCasC by looking up the relevant section of jenkins.yaml.

This time I won't repeat the same steps, but instead discuss the meaning of the entries more in depth:

  • Save the SSH private key as a credential in the Jenkins credentials store:
redentials:
system:
domainCredentials:
- credentials:
- basicSSHUserPrivateKey:
description: "firewalled-agent-robot_acct-priv"
id: "firewalled-agent-robot_acct-priv"
privateKeySource:
directEntry:
privateKey: "{AQAAABAu4YD...UN8IhfZyc5nQi}"
scope: SYSTEM
username: "robot_acct"

As discussed before, privateKey is stored as an encrypted value, and only the current Jenkins has the...