Hi community, We are discussing the architecture for Jenkins in our company. Our forecast is to have something around 500 jobs, each with average running time of 3 minutes.
We need a high availability environment, and we can not prevent the execution of new releases by the unavailability of the build server server or a very large queue builds awaiting execution. A single master and adding slaves on demand would be a good strategy for our scenario? How could we have a master with high availability? A cluster of jenkins master? Or load balance? Anyway could be necessary every jenkins master points to the same JENKINS_HOME? Suggestions? Someone has gone through a similar scenario? Regards. Marcus Vinicius A. Silva *P* *ANTES DE IMPRIMIR pense em sua responsabilidade e compromisso com o MEIO AMBIENTE.*
