Well, with Gradle we can provide per-task memory settings. But I think that requires forking?
Overall I think we should look into how to best leverage Gradle for improving time to run the tests anyway, part of which might be forking batches. On 03/28/2013 10:16 AM, Strong Liu wrote: > any hard ware spec available? > the hibernate-orm master is failing due to OutOfMemory and I tried to change > it to 1024M and faild > > maybe you can suggest a JAVA_OPTS? > > On Mar 28, 2013, at 12:54 AM, Sanne Grinovero <sa...@hibernate.org> wrote: > >> First delete all files in /etc/apache2/sites-enabled/ >> then create: >> >> /etc/apache2/sites-enabled/default >> >> with contents: >> >> <VirtualHost *:80> >> ServerName ci.hibernate.org >> ProxyRequests Off >> >> <Proxy http://localhost:8081/*> >> Order deny,allow >> Allow from all >> </Proxy> >> >> ProxyPreserveHost on >> ProxyPass / http://localhost:8081/ >> ProxyPassReverse / http://localhost:8081/ >> </VirtualHost> >> >> HTTPD modules to enable (commands to run): >> a2enmod proxy >> a2enmod proxy_http >> >> In /etc/default/jenkins change these only: >> HTTP_PORT=8081 >> PREFIX= >> (yes this value is empty) >> >> Then closed all ports except 80 on the AWS security group. >> >> Sanne >> >> >> >> On 27 March 2013 15:23, Davide D'Alto <daltodav...@email.it> wrote: >>> Good work, >>> what configuration have you applied to apache? I'm asking so that I can >>> apply that to the puppet scripts >>> >>> Davide >>> >>> >>> On Wed, Mar 27, 2013 at 1:51 PM, Sanne Grinovero <sa...@hibernate.org> >>> wrote: >>>> You're all welcome to play with http://54.225.162.168/ >>>> however please keep these in mind: >>>> >>>> - it's not the final machine: don't put too much effort in creating >>>> nice build scripts as we'll reset it to clean state soon. We *might* >>>> be able to store jobs defined so far, but we might choose not to. >>>> >>>> - domain name should be coming: ci.hibernate.org ..not sure when, got >>>> no replies so far from. >>>> >>>> - authentication: just click on login, it will use OAuth2 to request >>>> your identity via your GitHub account. Permissions to create new jobs, >>>> edit existing jobs, run a build manually depend on your github account >>>> be part of the Hibernate organization (or not, in which case you have >>>> read only status) >>>> >>>> At this stage I'd like to get a feeling if the hardware is powerful >>>> enough, and also we need to select which other plugins we want to use, >>>> I'm looking especially to: >>>> - static analysis reports >>>> - pull requests integration >>>> >>>> both are relatively undefined, we can of course start simple and >>>> improve later.. just checking this fits basic needs now. >>>> >>>> Sanne >>>> _______________________________________________ >>>> hibernate-dev mailing list >>>> hibernate-dev@lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev >>> >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > ------------------------- > Best Regards, > > Strong Liu <stliu at hibernate.org> > http://about.me/stliu/bio > > > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev