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

Reverting back to the original Jenkins

If you don't want to keep this Jenkins, it's easy to go back to the old one – simply delete the current controller and run the original again. Since everything in Jenkins is a flat file on the controller, all the configurations have persisted. You won't have to reconfigure anything, and you'll be back to right where you left it:

controller:~$ docker stop jcasc_controller 
controller:~$ docker rm jcasc_controller 
controller:~$ docker run \
--detach \
--restart on-failure \
-u $(id -u):$(id -g) \
-v ~/jenkins_home:/var/jenkins_home \
-p 8080:8080 -p 50000:50000 \
--name jenkins_controller \
calvinpark/jenkins:2.263.1-lts

Open a browser and navigate to the Jenkins URL. You should be able to log in as adder-admin and start adding more pipelines to the adder folder. If you're familiar with Docker commands, you can run multiple Jenkins instances on the same machine...