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

Posted to infrastructure-issues@apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2016/02/20 05:23:18 UTC

[jira] [Commented] (INFRA-11293) More Travis CI capacity for ASF projects

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

Wes McKinney commented on INFRA-11293:
--------------------------------------

What do you recommend in the meantime for other ASF projects which are presently being negatively impacted by Flink's (and the other top few projects') CI utilization? Thank you for your response.

> More Travis CI capacity for ASF projects
> ----------------------------------------
>
>                 Key: INFRA-11293
>                 URL: https://issues.apache.org/jira/browse/INFRA-11293
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: Github
>            Reporter: Wes McKinney
>
> As reported in FLINK-3452, high Travis utilization by a small subset of ASF projects on GitHub has challenged developer productivity on smaller projects with faster builds.
> Here is a total duration in seconds for each of the apache's active projects for the last 180 days (provided to me by Travis CI): https://gist.githubusercontent.com/drogus/d01a02aa9e0f7c380bde/raw/05be62eb1dd76085dd6cc9740e496ac2a111bc33/duration-by-project.txt
> I would suggest increasing our capacity beyond the 30 concurrent workers currently available or exploring procuring dedicated build slaves for projects with high overall utilization.



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