Replied inline...
> -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 23, 2005 3:16 PM > To: 'Maven Users List' > Subject: RE: Clustered Maven? > > Hi Jared, > > No this is something that would sit on top of Maven. > Currently Maven does > not provide the continuous build loop. For this you can use > CruiseControl, > Gump, DamageControl, etc. Some of these tools support the build queue > concept. In the future Maven will have its own continuous > build (it's in > development and called Continuum). We are using CruiseControl already. Works great... I'm hoping to drive Maven from CC. > > From an architecture standpoint, I would prefer to let the > different build > machines grab a build job. It's hard for a central point to > know the state > of the different build machines whereas the machine itself is > the best to > know its state. This allows to mix machines with different CPUs, RAM, > processors, etc. You get no failover this way. If machine X dies, the builds can't run until someone restores the machine. That is not acceptable in our environment. To give you a little more background, I'm thinking about a several hundred developers, 300 projects (plus installers) and about 5 millions lines of code. (SAS is big). http://www.pragmaticautomation.com/cgi-bin/pragauto.cgi/Build/CCOnALargeScale.rdoc We could put builds 1 through 17 on a single machine, 18 through 30 on another, etc, but if/when a single machine crashes, the recovery time would become a real issue. Also, you can't load balance this way. Someone would end up "tuning" the load to get projects that run in parallel off of the same machine. As to "knowing the state", if the proxy/manager issues the job and is notified (return code? Good log file?) of the job's completion, it's pretty easy to keep track of state. CPU, ram, etc becomes a side issue if you just issue one build at a time to each box in the cluster. Once a box is finished, you send another job. The faster boxes process more builds and the slow ones process less. Automatic load balancing. > > See > http://blogs.codehaus.org/people/vmassol/archives/000937_unbre > akable_builds. > html to see what I mean (forget the unbreakable part as this > is not our > topic here - just look at the build queue and the machines). Thanks. I had actually read that beofore. Your Binary Dependency Builds entry (http://blogs.codehaus.org/people/vmassol/archives/000953_binary_dependency_builds.html) is what convinced me that Maven might be able to handle a setup this big. Thanks! -Jared --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
