3
votes

In my company we are currently running Jenkins in a traditional master/slave setup for CI. We have 1 master and 4 slaves, so a fairly small setup.

2 of the slave boxes are high-powered VMs to run HP Fortify security scanning, which is fairly resource-hungry: it maxes out the VMs resources.

Due to increasing numbers of development teams wishing to utilise this model, we're looking to move to a distributed CI model, where each team runs their own CI infrastructure, but keep the high-powered VMs as they are (they are harder to acquire with our current company setup).

My question therefore is:

Is there a way to have multiple Jenkins masters connect to the same slave VM in such a way as they know about currently running jobs of other (unknown) Jenkins masters, and can queue as a result?

Any advice would be greatly appreciated.

2

2 Answers

2
votes

If your team grows as your infrastructure i think you could afford to use Jenkins Operation Center from CloudBees.

It support share slaves

0
votes

With right configuration several masters can be running on the same machine.

As for inter-master configuration it's little more complicated. Part of it could be obtained by OSS plug-ins like:

But most of all you should answer yourself why not utilize single master instead.