infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <>
Subject [jira] [Commented] (INFRA-13634) Make Travis fair use for all apache projects
Date Thu, 09 Mar 2017 22:14:38 GMT


Gavin commented on INFRA-13634:

Just a question - what does Travis do for your project that our our Jenkins does not?
Our Travis usage is still confined to 30.

Understanding why you would rather use Travis over our Jenkins would help me understand better
how we can improve things.

> Make Travis fair use for all apache projects
> --------------------------------------------
>                 Key: INFRA-13634
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Github
>            Reporter: Carlos Santana
>            Assignee: Daniel Takamori
>            Priority: Critical
> Currently using Travis is frustrating to wait sometimes 20 hours to get a pull request
build in Travis. At this rate is counter productive for committer and contributors, we want
to have continuous testing. waiting 20 hours is not.
> From this blog post in 2015 [1] it claims that Apache has 30 concurrent builds
> There is no way to tell in Travis if this is true? 
> Is INFRA still paying for the 30?
> I'm member of Apache OpenWhisk and Apache Cordova [~shazron] , and both projects
> will like to request if we can enable the Travis dedup [2] beta feature to ALL apache
repositories in Travis under the apache organization.
> One repo [3] has this feature enable, but doesn't make an impact if the rest of the repositories
are enable also.
> The request was greatful handle by [~pono] [4] to enable our repo, but we have more repos
to transfer for OpenWhisk.
> We would really appreciate if we can make Travis usable.
> --Carlos & Shaz
> [1]
> [2]
> [3]
> [4]

This message was sent by Atlassian JIRA

View raw message