On 28 June 2012 13:29, Marcus Vinicius <[email protected]> wrote: > 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.
Not to large an instance, but not small either > > 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? Some of the cloud provider plugins can help with adding slaves on demand > > How could we have a master with high availability? You might be interested in Jenkins Enterprise 12.05 from CloudBees, which has HA. There are limitations, IOW if the master goes down a standby will start up straight away... you will still have to wait for the job configuration to load, so it is not instant, and builds in progress will be lost, but we hope to remove and reduce these limitations over time. > A cluster of jenkins > master? Or load balance? Anyway could be necessary every jenkins master > points to the same JENKINS_HOME? > You cannot run multiple (active - the cloudbees HA feature ensures 1 active with N standby) jenkins instances off the same home at the same time > Suggestions? Someone has gone through a similar scenario? > You could pay somebody else to run the master for you and then let them provide you with a near infinite pool of slaves so that no job is stuck waiting... but you might not like giving away the control of your master to a Jenkins as a Service provider > > Regards. > > Marcus Vinicius A. Silva > > P ANTES DE IMPRIMIR pense em sua responsabilidade e compromisso com o MEIO > AMBIENTE.
