Just spotted the build is failing with an OutOfMemoryError
- Code: Select all
FATAL: Java heap space
java.lang.OutOfMemoryError: Java heap space
There are some suggestions and solutions here
Sorry for the slow response, I have been on holiday.. However because of linux kernel updates I've restarted the server on Saturday, after that all builds are fine again. The bad thing is that I'm not sure what caused the error. Let's just wait and see if it hits us again..
TheLQ wrote:Once the kinks get worked out it would be nice have an easy, quick process to get forks into Jenkins, IE forks like my VLC project. They would probably be temporary but it would make things very easy since you can say "Hey, I just changed X, can you all test it before it gets merged upstream?"
Also if your in need of more processing power I have at least one server I could donate to the cause as a build node. PM if interested
After all Jenkins does "only" a full build of a fork. To verify that the build is working, a local 'mvn clean package' would be enough (and IMHO is mandatory before committing anything). So Jenkins primary target are forks that "live" at least a few weeks and should be tested by users. Another reason would be to track the amount of find bugs warning over time.
For that purpose a simple request in this thread would do the trick and I will setup a new Jenkins job. All I need is:
- the repository to use
- the branch to checkout
- location of the pom.xml to use
- the maven build goals you prefer (e.g. 'mvn clean package')
Please understand that due security reasons I don't want to give other users admin access to Jenkins on my server at the moment. That might change in the future.
The processing power is only a problem when using the 'site' goal that includes e.g. findbugs that needs more than 1gb of ram. But I like your idea of using slaves to distribute the load. I've never done this with Jenkins but if you like you can setup a slave and I'll try to integrate it.