You are viewing a plain text version of this content. The canonical link for it is here.

Posted to infrastructure-issues@apache.org by "Geoffrey Corey (JIRA)" <ji...@apache.org> on 2015/08/11 20:47:48 UTC

[jira] [Updated] (INFRA-10092) Add CNAME for an external Bigtop's CI master server

     [ https://issues.apache.org/jira/browse/INFRA-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey Corey updated INFRA-10092:
-----------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

> Add CNAME for an external Bigtop's CI master server
> ---------------------------------------------------
>
>                 Key: INFRA-10092
>                 URL: https://issues.apache.org/jira/browse/INFRA-10092
>             Project: Infrastructure
>          Issue Type: Task
>            Reporter: Konstantin Boudnik
>            Assignee: Geoffrey Corey
>
> 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 most preferably, ci.bigtop.apache.org



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)