Jump to content
Sign in to follow this  
justin nelson

Why can't Hudson run Maven?

Recommended Posts

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.

Share this post


Link to post

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.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
×