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

Script Security

The power and the flexibility of Jenkins come from the pipelines that can run Groovy code – a fully featured language independent of Jenkins. Since Jenkins pipelines allow Groovy code to be executed, a pipeline can do nearly anything that Groovy can do. The Difference from plain Groovy section in the Jenkins User Handbook lists just one difference, that some Groovy idioms are not fully supported because the pipeline code must be serialized1. Allowing us to use a real programming language, as opposed to twisting an inflexible DSL that is not designed to be a general-purpose language, provides amazing power and flexibility. With great power, of course, comes great responsibility. Take this pipeline, for example:

pipeline {
    agent any
    stages { stage ('Destroy') {
      steps { script {
            Jenkins.instance.items.each { 
 ...