Building Jenkins master
We already have a custom slave image. Why would we also want to build our own master image? One of the reasons might be that we don't want to use slaves at all, and, since the execution would be done on master, its environment has to be adjusted to the project's needs. That is, however, a very rare case. More often, we will want to configure the master itself.
Imagine the following scenario, your organization scales Jenkins horizontally and each team has its own instance. There is, however, some common configuration, for example: a set of base plugins, backup strategies, or the company logo. Then, repeating the same configuration for each of the teams is a waste of time. So, we can prepare the shared master image and ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access