Distributed builds using Jenkins
In the previous chapters, we saw how to configure Jenkins on node machines. These node machines act as Jenkins slaves. So far, we have configured Jenkins on two nodes, one for testing the code (the testing server) and the other to host the live application (the production server). However, we used the Jenkins master server to perform all our Jenkins builds.
Executing builds on the Jenkins master server may seem to be fine as long as you have sufficient hardware configuration for the Jenkins master server. Nevertheless, imagine a situation where the number of builds per day increases from single digit to multiple digits. What would happen to the Jenkins master server?
The builds may execute slowly, one after the other, since everything is happening on a single machine, which is the Jenkins master server
Total build time may increase due to CPU load, assuming we do not upgrade the Jenkins master server
We may face disk space issues. As the number of builds per...
