Yes, I didn't find the time yet to see how to set the MAVEN_OPTS in the hudson build. I'll try to figure it out now.
On 08.07.2010 23:53, David Carver wrote: > My experience with ODE and Hudson builds regardless if it's Maven or > Buildr you need to specify at least the JVM option of > -XX:MaxPermSize=256m if you are using a Sun JVM for the build. > > It also helps to specify, -Xmx2048m -Xms512m > > I've in the past set up a Parameter based build, with JAVA_OPTS and the > values of: > > -XX:MaxPermSize=256m -Xmx2048m -Xms512m > > The permgen errors typically happen during Hibernate code generation steps. > > Dave > > > On 07/08/2010 02:39 PM, Antoine Toulme wrote: >> FYI. This is the second time this happens. I also had to kill a build >> yesterday that used maven. >> >> ---------- Forwarded message ---------- >> From: sebb<[email protected]> >> Date: Thu, Jul 8, 2010 at 14:36 >> Subject: [Hudson] ODE-trunk-m2-jdk5-nightly-deploy » #7 stuck, so >> killed it >> To: [email protected] >> >> >> ODE-trunk-m2-jdk5-nightly-deploy » #7 was stuck - it had run out of >> PermGen space. >> >> Hudson should have tidied up, but did not, so I killed the job a few >> times from the GUI and it seemed to recover. >> >> Not sure why Hudson can do this itself ... >> > -- Tammo van Lessen - http://www.taval.de
