I have been facing this error because of large build output files created by builds in my projects. The logs have a threshold of INFO and they do create large files even then because of the sheer size of the project.
This causes OutOfMemory errosr in two places: 1) The webapp - When we click on the build results page (And if the build output file is huge) 2) The Reports Generation phase (Usually towards the end of the build) - This is a major problem. Because the build does not complete even though it has run all the phases till Test. And the result is that we dont have the surefire reports link in the build result page and also there is no notification email sent out. For now, in my project, i have just put in a check for the size of the file and if it is larger than 50MB, i just put in a messsage that the file is Huge. This may not be an ideal patch for this problem. So the questions i have are: 1) Can't we avoid reading the files into a String during report generation? 2) In the build results page, we can have a save file button instead of opening the whole file in memory? 3) Is there any way we can continue the reports generation of a failed Build? I am pretty sure it is not possible today. But , maybe in the future, we can have some flexibility that, even though the Build failed in say phase 3 after successful completion phase 1 and 2, we should be able to continue from phase 3. This will be very useful and we can have the full builds even though it didnt run correctly during the scheduled time. Any suggestions? What do people think of my patch? Should I submit it? Murali.
