www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Schaefer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7017) Jenkins Master VM for ATS
Date Thu, 27 Feb 2014 01:40:20 GMT

    [ https://issues.apache.org/jira/browse/INFRA-7017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913891#comment-13913891

Joe Schaefer commented on INFRA-7017:

I am frustrated by EVP's comments in this issue.  This has nothing to do with cost as he's
not intending to bring his slaves in house, he just wants his own master largely for reasons
that don't further the mission of infra to provide common services for everyone's enjoyment.
 If there needs to be a bigger budget for our build farm than I'd prefer to see EVP engage
at that level than to get directly involved in the nuts and bolts of things he doesn't have
a clue about.

> Jenkins Master VM for ATS
> -------------------------
>                 Key: INFRA-7017
>                 URL: https://issues.apache.org/jira/browse/INFRA-7017
>             Project: Infrastructure
>          Issue Type: New Feature
>          Components: Jenkins
>            Reporter: Leif Hedstrom
>            Assignee: Gavin
>             Fix For: Initial Clearing
> The Apache Traffic Server project have some dedicated boxes running our CI infrastructure.
We will continue to do so, but would like to move the Jenkins Master back to an ASF hosted
VM. Ideally dedicated for our Jenkins, we have a *lot* of build bots, for a lot of branches.
> The main reason for pulling this back is for stability and security. We use TLS (https://ci.trafficserver.apache.org/)
with a self signed cert right now, and that is not good. By hosting the master on an ASF VM,
we're hoping we can get an official SSL certificate for ci.trafficserver.a.o as well.

This message was sent by Atlassian JIRA

View raw message