We have a single Jenkins Master running on linux 64-bit machine with 6 Gigs of ram allocated for the Jenkins VM. We have 700+ jobs and 50+ slaves (all OS's (windows/mac/linux/freebsd/etc/), and all connected via ssh), and we always have a build running. Only on rare occasions is Jenkins not doing anything.
We have it setup to poll our SCM (snv and perforce) every hour, and if there are changes, it kicks off the appropriate build job. We almost never have to reboot Jenkins. I think the only time we need to bring Jenkins down is when there is a fancy plugin that we want to use, and when that happens we schedule the downtime so that the development team is aware of it. I developed my own "slaves on demand" script that I connected to our Lab Manager, but it only gets used if there are no existing slaves that can handle the job. Overall, it's a pretty stable system, considering all the stuff that it's doing! -- View this message in context: http://jenkins.361315.n4.nabble.com/Jenkis-with-high-availability-tp4633085p4633132.html Sent from the Jenkins users mailing list archive at Nabble.com.
