Oh you really meant you want your slaves to HA! Usually people just have so many slaves it doesn't matter if some go down.
-- Sami Matteo Centonza <mat...@metatype.it> kirjoitti 4.2.2013 kello 16.37: > Hello Sami, Rob, > > thanks for your replies. > > We are currently using redhat cluster to provide failover capabilities to > jenkins master. > > Haven't tried Cloudbees Jenkins Enterprise either but from what' i've read, i > assume failover > capabilities are restricted to master failover, so functionally equivalent to > what we have already > achieved. > > I can't find any reference on slave resiliency in the event of a master > failure, but i'll be really glad > to be corrected from someone more knowledgeable than me on the enterprise > product :) > > A presto, > > -m > > > 2013/2/4 Mandeville, Rob <rmandevi...@litle.com> >> If you’re willing to pony up some money, you should talk to Cloudbees >> regarding their Enterprise version >> (http://www.cloudbees.com/jenkins-enterprise-by-cloudbees-overview.cb). I >> haven’t tried it (yet), but it comes with several plugins you can’t get >> otherwise, and one of them is a High Availability plugin. This specifically >> allows you to fail over to a second Jenkins master on the fly if the master >> dies. >> >> >> >> --Rob >> >> >> >> From: jenkinsci-users@googlegroups.com >> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Matteo >> Sent: Tuesday, January 22, 2013 2:24 PM >> To: jenkinsci-users@googlegroups.com >> Subject: jenkins clustering >> >> >> >> Hello, >> >> >> >> first i'd like to thank developers for this great project. >> >> >> >> I'm sorry if already asked but i'm new on this list and searching the web >> has produced no results. >> >> >> >> We have a jenkins installation with 1 master and 5 slaves connected through >> ssh. >> >> >> >> We are mostly a java shop and jenkins is central to our infrastructure since >> we >> >> build and deploy releases to servers from it. >> >> >> >> For this reason slave resiliency in the face of master failure is paramount >> to us. >> >> >> >> My question: >> >> Is there a way, in a master/slave configuration, to have slave builds >> running to completion even in case of master failure (ideally refetching >> console logs once the master is back up :))? >> >> >> >> In our current setup, we get a proxy error on master UI and builds are >> aborted. >> >> >> >> Thanks in advance for any hint, >> >> >> >> -m >> >> The information in this message is for the intended recipient(s) only and >> may be the proprietary and/or confidential property of Litle & Co., LLC, and >> thus protected from disclosure. If you are not the intended recipient(s), or >> an employee or agent responsible for delivering this message to the intended >> recipient, you are hereby notified that any use, dissemination, distribution >> or copying of this communication is prohibited. If you have received this >> communication in error, please notify Litle & Co. immediately by replying to >> this message and then promptly deleting it and your reply permanently from >> your computer. >> -- >> 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. >> For more options, visit https://groups.google.com/groups/opt_out. > > -- > 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. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
