[
https://issues.apache.org/jira/browse/FLINK-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362683#comment-15362683
]
Robert Metzger commented on FLINK-4151:
---------------------------------------
Regarding our 10 slots, we could ask Apache to increase our limit a bit, if
this is getting a problem. I'm using travis with my own GitHub account for my
work, so I don't care too much for the apache/flink account. Since it usually
takes around 24 hours until we start looking at pull request, there is plenty
of time for travis to run the tests.
There are tools to cancel old builds of pull requests:
https://github.com/grosser/travis_dedup. The problem is that Travis doesn't
have access tokens for individual repositories, only for the entire travis
account. I don't think that Apache Infra will give us the access token for the
Apache travis account.
But maybe we can talk to infra and see if they can offer this as a service for
all ASF Travis users?
I think we've paralleled the builds as much as possible (using concurrent test
execution in maven).
> Address Travis CI build time: We are exceeding the 2 hours limit
> ----------------------------------------------------------------
>
> Key: FLINK-4151
> URL: https://issues.apache.org/jira/browse/FLINK-4151
> Project: Flink
> Issue Type: Task
> Components: Build System
> Reporter: Robert Metzger
> Assignee: Robert Metzger
> Attachments: Pasted image at 2016_07_04 16_31.png
>
>
> We've recently started hitting the two hours limit for Travis CI.
> I'll look into some approaches to get our build stable again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
