Re: [hibernate-dev] New CI machine preview

2013-03-28 Thread Strong Liu
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 wrote: > First delete all files in /etc/apache2/sites-enabled/ > then create: > > /

[hibernate-dev] IRC Developer Meeting - 3/28

2013-03-28 Thread Steve Ebersole
[10:33] Meeting ended Thu Mar 28 15:28:23 2013 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) [10:33] Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-03-28-14.56.html [10:33] Minutes (text): http://transcripts.

Re: [hibernate-dev] New CI machine preview

2013-03-28 Thread Steve Ebersole
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 har

Re: [hibernate-dev] New CI machine preview

2013-03-28 Thread Sanne Grinovero
As far a hardware specs, today it's a c1.medium [1], we can change that at any time to any machine described on the same page, but of course it has an impact on costs. But I'm missing how hardware specs could be related, possibly I'm not understanding how gradle works. >From the build script it l

Re: [hibernate-dev] New CI machine preview

2013-03-28 Thread Gunnar Morling
Hi, I just came across an interesting Jenkins plug-in which promises to make 2013/3/27 Sanne Grinovero > 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

Re: [hibernate-dev] New CI machine preview

2013-03-28 Thread Gunnar Morling
Fat fingers... another try ;) Hi, I just came across an interesting Jenkins plug-in which promises to make EC 2 spot instances usable for Jenkins jobs [1]. I haven't tried it out myself, but this might be an interesting way to get build power at a lower price from the EC 2 spot market. --Gunnar