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

Upgrading plugins using Plugin Manager

We'll upgrade our Jenkins using the first strategy. We are upgrading from one newish LTS version to the next LTS version, therefore we're not expecting any plugin version incompatibility issues. Even so, to minimize the possibility, let's upgrade all the plugins before upgrading the controller.

Log in to Jenkins as the admin user, click Manage Jenkins, and then Manage Plugins. On the Updates tab, check all the boxes that are available for an upgrade. In Figure 8.4, notice that LDAP cannot be upgraded because version 2.4 is not compatible with the current version of Jenkins. But wait a minute. The current version of the LDAP plugin is 1.26, which is far back from 2.4. Would version 2.0, 2.1, 2.2, or 2.3 be compatible with the current Jenkins? How do we look up the version compatibility chart for older versions of a plugin?

Figure 8.4 – Not all plugins can be upgraded due to version...