community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tony Stevenson <t...@pc-tony.com>
Subject Re: CNAME for an external CI host
Date Sat, 08 Aug 2015 22:55:33 GMT



Cheers,
Tony

Sent from my iPhone - Please excuse any brevity or typos. 



> On 8 Aug 2015, at 23:52, Konstantin Boudnik <cos@apache.org> wrote:
> 
> Thanks Tony - that was the intention, but I thought there might be a different
> processes for that, so I came to comdev@
> 

Nahh this is a technical issue - drop a new infra issue in JIRA and we'll get back to you.


> Regards,
>  Cos
> 
>> On Sat, Aug 08, 2015 at 11:43PM, Tony Stevenson wrote:
>> Perhaps asking on the infra list - seeing as this is an infrastructure
>> question - would be a good start ? 
>> 
>> We have other instances of external services using an apache.org address. I
>> don't recall the rules we have for this offhand but if you open a JIRA issue
>> it will get the appropriate attention. 
>> 
>> 
>> Cheers,
>> Tony
>> 
>> Sent from my iPhone - Please excuse any brevity or typos. 
>> 
>> 
>> 
>>> On 8 Aug 2015, at 20:48, Konstantin Boudnik <cos@apache.org> wrote:
>>> 
>>> I am not sure if this is the right place to ask, but I don't know of any
>>> better one. So here it is. 
>>> 
>>> At Bigtop project we have a number of hosts sitting on AWS and running some
>>> intensive CI for the project: building packages, spinning up the clusters,
>>> and testing them. For the consistency of the deployment recipes we'd like to
>>> have a CNAME for the CI master to be in the form of bigtop-ci.apache.org or,
>>> better yet, ci.bigtop.apache.org
>>> 
>>> Is is a normal practice for the INFRA to setup such thing? Would be there any
>>> concerns about such a schema from the community stand-point?
>>> 
>>> Thanks in advance
>>> Cos

Mime
View raw message