jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davide Giannella (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1855) Travis builds time out
Date Tue, 05 Aug 2014 13:44:12 GMT

    [ https://issues.apache.org/jira/browse/OAK-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086276#comment-14086276

Davide Giannella commented on OAK-1855:


The usage of multiple profiles moves the ownership of the build to
maven rather than to travis and gives clearer output on the travis
console (at least IMO). :)

I've changed again the build for having 1 integration testing profile
and you can see the output of the related build at
(currently building).

*In a nutshell*

{{pedantic}} runs: rat, findbugs and checkstyle (as ever) but skip the
unit testing

{{unittesting}} runs all the unit tests against all the available

{{integrationTesting}} by default runs all the unittests and
integration tests against Segment. Overridden in the build for
skipping the UT and splitting Segment from Document* fixtures. Should
be more easily integrated into the check-release.sh if needed for
testing at least against Segment.

{{clean install}} will run the unit testing against Segment only.

> 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
>            Assignee: Davide Giannella
>         Attachments: OAK-1855-ut-times.txt
> 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

View raw message