www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leif Hedstrom (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7017) Jenkins Master VM for ATS
Date Thu, 21 Nov 2013 17:17:38 GMT

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

Leif Hedstrom commented on INFRA-7017:

Well, looking at builds.apache.org vs ci.trafficserver.apache.org, I really would prefer a
view like the second one. We'd add about 60-100 build queues to the system, and we expect
it to grow. And we need to have a way to watch them all in some manageable way.

If you can provide a view like the one at http://ci.trafficserver.apache.org, then that's
great, and it doesn't matter which box it's on :).

I hope that makes sense?

> 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
> 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