Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Jenkins Administrator's Guide
  • Table Of Contents Toc
  • Feedback & Rating feedback
Jenkins Administrator's Guide

Jenkins Administrator's Guide

By : Calvin Sangbin Park , Adithya, Sam Gleske
4.4 (7)
close
close
Jenkins Administrator's Guide

Jenkins Administrator's Guide

4.4 (7)
By: Calvin Sangbin Park , 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)
close
close
12
Index

Other ways to reduce agent log output

Part of solving agent bottlenecks related to logs for Jenkins can come from training users on how to reduce log output within their builds. While this might not scale uniformly across all user pipelines in a very large environment, every little bit of optimization helps.

Strategy – Writing logs to the agent disk

One strategy could be to write more verbose logs to disk on the agent, compress them on the agent, and then archive them for later viewing by the user to debug issues. This helps to drastically reduce the amount of data streamed to the controller as logs because plain text data compresses really well.

Benefits include the following:

  • A faster build time because processes write logs to files on disk faster than the agent can stream logs to the Jenkins controller.
  • Less data streamed to the controller means less load on the network and less storage used by $JENKINS_HOME when compressed logs are uploaded...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY