Why can't Hudson run Maven?

[justin nelson 15]

All of my Hudson builds are failing. The following is the build output:

Why can’t enough heap space be created? What can I do to fix it?

[Guest mrdavidlaing]

RDP to the Java build slave (184.73.198.149) and set the following global environment variable:

MAVEN_OPTS = -Xmx256m -XX:MaxPermSize=256m

(see http://maven.apache.org/maven-1.x/reference/command-line.html for some further details. I can’t find the relevant Maven 2.x documentation for this feature)

The build slave is currently running on an EC2 micro instance which only havs 690MB of RAM; so it you’re still having issues we’re going to have to bump this up to a large EC2 instance.

[justin nelson 15]

RDP to the Java build slave (184.73.198.149) and set the following global environment variable:

MAVEN_OPTS = -Xmx256m -XX:MaxPermSize=256m

(see http://maven.apache.org/maven-1.x/reference/command-line.html for some further details. I can’t find the relevant Maven 2.x documentation for this feature)

The build slave is currently running on an EC2 micro instance which only havs 690MB of RAM; so it you’re still having issues we’re going to have to bump this up to a large EC2 instance.

I was able to fix this by just giving the crap4j plugin more memory in the POM. I think I will just leave it that way for now. If we run into more errors I will set the global parameter.