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 <sanne(a)hibernate.org&gt; 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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev

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 <sanne(a)hibernate.org&gt; 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 <daltodavide(a)email.it&gt; 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 <sanne(a)hibernate.org&gt; >> 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(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

I'm not against a rename, but in terms of consistency I noticed only the java projects (jars we distribute) have such a prefix. Websites and other infrastructure does not (in.relation.to awestruct) You want to rename that too? On 3 April 2013 13:16, Emmanuel Bernard <emmanuel(a)hibernate.org&gt; wrote: > Thanks guys, nice tough on the OAuth - GitHub integration. > > I have a proposal: can we rename the Git repo hosting the configuration > to hibernate-continuous-integration or hibernate-ci? > > I'm specifically asking because GitHub is not quite consistent in > whether or not it shows the organization it comes from and prefixing > repository with their upbrella org is a good practice we are using at > the moment. > > Emmanuel > > On Wed 2013-03-27 13:51, Sanne Grinovero 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(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hibernate-dev >

Thinking about the domain name, would you prefer - hibernate-ci - ci.hibernate.org ? I feel in some way the name should convey it's not a standard java project as all other repositories starting by hibernate-, and clarify we didn't make our own CI tool :-) Sanne On 3 April 2013 14:03, Emmanuel Bernard <emmanuel(a)hibernate.org&gt; wrote: > The reason in.relation.to does not is because in.relation.to is uniquely > identifiable as a name (it's a domain name). This would not be the case > for 'search' as > opposed to 'hibernate-search'. > > On Wed 2013-04-03 13:33, Sanne Grinovero wrote: >> I'm not against a rename, but in terms of consistency I noticed only the >> java projects (jars we distribute) have such a prefix. >> Websites and other infrastructure does not (in.relation.to awestruct) >> You want to rename that too? >> >> >> On 3 April 2013 13:16, Emmanuel Bernard <emmanuel(a)hibernate.org&gt; wrote: >> >>> Thanks guys, nice tough on the OAuth - GitHub integration. >>> >>> I have a proposal: can we rename the Git repo hosting the configuration >>> to hibernate-continuous-integration or hibernate-ci? >>> >>> I'm specifically asking because GitHub is not quite consistent in >>> whether or not it shows the organization it comes from and prefixing >>> repository with their upbrella org is a good practice we are using at >>> the moment. >>> >>> Emmanuel >>> >>> On Wed 2013-03-27 13:51, Sanne Grinovero 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(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

On 3 Apr 2013, at 20:34, Sanne Grinovero <sanne(a)hibernate.org&gt; wrote: > Thinking about the domain name, would you prefer > - hibernate-ci > - ci.hibernate.org +1 for ci.hibernate.org. I also like that it not reflect Jenkins in its name. --hardy _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

On 3 avr. 2013, at 21:14, Hardy Ferentschik <hardy(a)hibernate.org&gt; wrote: > > On 3 Apr 2013, at 20:34, Sanne Grinovero <sanne(a)hibernate.org&gt; wrote: > >> Thinking about the domain name, would you prefer >> - hibernate-ci >> - ci.hibernate.org > > +1 for ci.hibernate.org. I also like that it not reflect Jenkins in its name. I like it too and it seems the norm for other projects I have seen.

I've also updated the url of the project on the ec2 machine. The machine has also a tag Name=ci.hibernate.org, right now is not very important but if in the future there are multiple machines it may be helpful. By the way, the job that build search on jenkins is now using the settings-example.xml for the build and the global settings.xml does not currently contain the redhat repository. On Thu, Apr 4, 2013 at 9:16 AM, Sanne Grinovero <sanne(a)hibernate.org&gt; wrote: > > Ok, done. > Assuming Davide renames his own repo too, remember to run: > > git remote set-url sanne git@github.com:Sanne/ci.hibernate.org.git > git remote set-url davide git@github.com:DavideD/ci.hibernate.org.git > git remote set-url upstream git@github.com:hibernate/ci.hibernate.org.git > > + your own in case you had it already. > > > > On 4 April 2013 08:56, Emmanuel Bernard <emmanuel(a)hibernate.org&gt; wrote: > > > > > > > On 3 avr. 2013, at 21:14, Hardy Ferentschik <hardy(a)hibernate.org&gt; wrote: > > > > > > > > On 3 Apr 2013, at 20:34, Sanne Grinovero <sanne(a)hibernate.org&gt; wrote: > > > > > >> Thinking about the domain name, would you prefer > > >> - hibernate-ci > > >> - ci.hibernate.org > > > > > > +1 for ci.hibernate.org. I also like that it not reflect Jenkins in > > > its > > name. > > > > I like it too and it seems the norm for other projects I have seen. > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev