Re: [hibernate-dev] New CI machine preview

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