You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "David Nalley (JIRA)" <ji...@apache.org> on 2016/02/20 04:58:18 UTC

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

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

David Nalley closed INFRA-11293.
--------------------------------
    Resolution: Won't Fix

So according to the stats provided by Travis, Flink is responsible for more than 50% of the consumed time over the past 6 months. While we do want the current allocation to be consumed, at the going rate, where Flink is more than 3x the consumption of the next closest project, and infra does not currently plan on increasing our allocation with Travis.  I'd suggest the Flink PMC work with the President to secure dedicated funding for more resources in the upcoming budget if they feel they need more. That budget is already being planned. 


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