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

Displaying test results and a code coverage report

Required plugins

Cobertura, JUnit Plugin

We are already running unit tests, but we can't see the result unless we go into the console output and look for it. The test result can be exposed in a nicer format using the JUnit plugin. While we're at it, let's also add a code coverage report:

  1. Open the Jenkinsfile and update the Unit test stage to generate two XML reports, junit.xml for the unit test results and coverage.xml for the code coverage report:
    stage('Unit test') {
    steps {
    sh '''python3 -m pytest \
    -v --junitxml=junit.xml \
    --cov-report xml --cov adder adder.py
    '''
    } }
  2. Also, add a post directive in the Jenkinsfile to pick up the two report files. The post directive should be on the same level as the stages directive:
    pipeline {
    agent { ... }
    stages...