You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2014/07/25 10:46:38 UTC
[jira] [Commented] (OAK-1855) Travis builds time out
[ https://issues.apache.org/jira/browse/OAK-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074209#comment-14074209 ]
Davide Giannella commented on OAK-1855:
---------------------------------------
I'm not that expert in how to configure those stuff but I think we can
address this in two steps:
First split the build with multiple profiles to avoid it failing. I
would say to have a profile for unit test (mvn clean install), one for
pedantic (-P pedantic) and one for the integration testing (-P
integrationTesting). They should all be there. Is it possible?
The we can investigate the build itself drawing some stats from
previous build and address what can be addressed with individual
issues grouped by an epic.
Thoughts?
> Travis builds time out
> ----------------------
>
> Key: OAK-1855
> URL: https://issues.apache.org/jira/browse/OAK-1855
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Marcel Reutegger
>
> Recently quite many travis builds failed because they hit the 50 minutes time limit.
> Possible solutions that come to my mind:
> - reduce the time our tests take
> - split up the build with multiple profiles
--
This message was sent by Atlassian JIRA
(v6.2#6252)