That's not entirely accurate, I think. I have a job that builds Jenkins. The job is a maven job and I have set "-XX:MaxPermSize=256m -Djava.awt.headless=true" into MAVEN_OPTS under the Advanced button (in Build section). The build will fail without the permgen pool resize and also pop up some extra icons into the dock without the headless option. I'm definitely of the opinion Jenkins will launch a new JVM where it executes maven.
-- Sami Kanstantsin Shautsou <gentoo.inte...@gmail.com> kirjoitti 30.7.2012 kello 0.40: > Does it work for maven based jobs? > Looks like you can't set more memory for maven then you gave to jenkins > process, because maven executes in parent jenkins java process. > > 2012/7/26 Markward Schubert <markward.schub...@gmail.com> > Hi Group! > > Is there some known issue with JVM Parameters being ignored for Maven build > steps in freestyle jobs? I have the following parameters set: > > -XX:PermSize=128m -XX:MaxPermSize=512m -Xms512m -Xmx1g > > It seems that these are ignored, because when I put -Xmx8g, the build runs as > if i wrote 1g, although the machine has a total of about 4g of ram. > So I would expect the job to stop with a message, that i assigned more mem, > than available. > The reason for me to investigate in this is, because after activating the > checkstyle plugin, I start getting heapspace Exceptions and started to > experiment with these settings. > > >
