Summary
In this chapter, we saw how to use the distributed build architecture using Jenkins slaves to achieve load balancing. We can scale the Jenkins build cluster to any number of slaves by adding new Jenkins nodes and grouping them under an appropriate label. In any organization, audit plays an important role in identifying what caused an issue. This is where the Jenkins plugins named jobConfigHistory and Audit Trail come in handy. You might want to use both together. We also saw how to send notifications using the HipChat tool. We discussed how to configure Jenkins jobs to optimize disk usage by regular workspace cleanup.
Lastly, we saw how to use the Jenkins Simple Theme Plugin to make Jenkins visually appealing.
