Hi everyone,
There is a problem I have been struggling with Jenkins. I tried
different CI servers but none of them offers the same features Jenkins
has, so I want to use it.
I have a small Rackspace CloudServer instance with 256MB RAM and running
Jenkins with Apache Tomcat 7 in that server. Using Maven 2 and Git
plugins of Jenkins.
The problem is, either Maven JVM exits with the code 137 (when forking
is enabled) or I get mysterious crashes. I know that the 256MB of RAM
may not be enough for Jenkins; but the thing is: even when I am running
Jenkins, I can build the project via command line in a short period of
time. My project involves some heavy servers, and generally the test are
failing with Jenkins.
If I can build the project via command line just fine when the Jenkins
server is running (meaning more than one JVM), isn't that a problem with
the Jenkins? I tried different combinations of fork configurations and
Maven JVM settings, even when build is OK for once, then it fails in
subsequent builds.
I even set maximum number of builds to keep to 3, but it didn't help.
Any comments are appreciated.
Best regards,
Deniz
