If you have a spare server, you could setup a new master and front both the new and existing Jenkins master with Apache and have Apache handle the failover. I'm not sure about how this would affect slaves, but in theory this should work, or at least it's an approach I have used albeit not with Jenkins, and would certainly be very quick to test the configuration on a single server to prove the theory (i.e. install Apache and two Tomcat instances and deploy Jenkins to both Tomcat instances).
On Tuesday, November 27, 2012 4:45:25 AM UTC, zw wrote: > > Hi > > We have one Jenkins configured and it went down. > Our only Jenkins as 3 slaves. > We like to install another Jenkins acting as secondary master for the > 3 slaves nodes in case the primary master Jenkins goes down. > > Will this configuration work ? > Can multiple Jenkins work together ? > How do we configure secondary Jenkins such that when primary Jenkins > goes down, it takes over ? > How would the slaves know that the secondary Jenkins is in service and > not the primary Jenkins. > > Thanks for your help >
