any hard ware spec available?
the hibernate-orm master is failing due to OutOfMemory and I tried to change it to 1024M
maybe you can suggest a JAVA_OPTS?
On Mar 28, 2013, at 12:54 AM, Sanne Grinovero <sanne(a)hibernate.org> wrote:
First delete all files in /etc/apache2/sites-enabled/
Allow from all
ProxyPass / http://localhost:8081/
ProxyPassReverse / http://localhost:8081/
HTTPD modules to enable (commands to run):
In /etc/default/jenkins change these only:
(yes this value is empty)
Then closed all ports except 80 on the AWS security group.
On 27 March 2013 15:23, Davide D'Alto <daltodavide(a)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
> On Wed, Mar 27, 2013 at 1:51 PM, Sanne Grinovero <sanne(a)hibernate.org>
>> You're all welcome to play with http://22.214.171.124/
>> 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.
>> hibernate-dev mailing list
hibernate-dev mailing list