This chapter is all about Jenkins best practices. We will begin the chapter with the distributed builds, where we will see how to harness the Jenkins master-slave architecture to achieve load balancing while performing builds.
We will also see how to version control Jenkins system configuration and job configuration, along with auditing Jenkins. This will give us more control over Jenkins in the event of system failures.
Next, we will see how to connect Jenkins with communication tools to send notifications. This will give us an edge over the older e-mail-based notification system.
Lastly, we will discuss some other best practices related to Jenkins jobs and Jenkins updates. If some of you are not happy with the Jenkins GUI, there is section at the end to install Jenkins themes.
These are the important topics that we will cover in this chapter:
Creating a build farm using Jenkins slaves
Installing and configuring a jobConfigHistory plugin to version control Jenkins...