Managing nodes
Jenkins provides a master-slave concept for managing the aforementioned scenarios. We can assign different build jobs to different slaves in the build configuration and use the master-slave system to manage its overall lifecycle. The master node itself can execute the build if a slave node is not configured explicitly in the build job configuration.
There are quite a few reasons for using this feature:
- Build jobs require resources, and they compete for resource availability
- A different runtime environment is required for different build jobs
- It distributes the load across slave nodes
To make things clearer, we need not install Jenkins on the slave nodes. We only need to configure the slave nodes properly, which we will now cover.
The ...
Get DevOps for Web Development now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
