On Tue, Nov 17, 2009 at 7:20 AM, Simon Laws <[email protected]> wrote: > I raise this topic with some trepidation as we've been here before but > here goes. We have been building (and releasing) all of the code in > the 2.x code base which has worked well to date. However two things > make me pause for thought: > > - we are not running the otests as part of the main build and we are > already seeing regressions because of this (this will happen more > often as more otests are brought in). This is not good. > - my 2.x build (without otests) is already up to 45 minutes and there > are still more extensions to bring back in >
Here is some numbers that can help in case we want to optimize the current build as a first step. http://people.apache.org/~lresende/tuscany/Tuscany%20Build.pdf This is based on my build machine, which is taking 12 mins for a full 2.x build [INFO] Total time: 12 minutes 10 seconds [INFO] Finished at: Tue Nov 17 08:07:47 PST 2009 [INFO] Final Memory: 102M/210M [INFO] ------------------------------------------------------------------------ -- Luciano Resende http://people.apache.org/~lresende http://lresende.blogspot.com/
