[CloudBees Employee Hat] I suspect it is the workflow addition that we have whereby the workflow can continue running *while* you restart the master that you are after... that is something that is more valuable in my mind than HA... [/CloudBees Employee Hat]
On 28 November 2012 at 04:06, Jerry <gpjerrymalo...@gmail.com> wrote: > It is also possible to maintain your Jenkins config files in source > control. We could very quickly get a new instance of Jenkins up and running > just by cloning our SCM repository to a new machine and dropping the > Jenkins WAR in the right place. > > But I have to second Rob Mandeville's suggestion to at least look into the > Cloudbees high availability plugin. > > -- Jerry > > > > On Monday, November 26, 2012 11:45:25 PM UTC-5, 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 >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMxvNWWCTDiho35KaGsUNFegd4NedUOSf0P954iw_p8inw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
