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/08/05 15:52:13 UTC

[jira] [Comment Edited] (OAK-1855) Travis builds time out

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

Davide Giannella edited comment on OAK-1855 at 8/5/14 1:51 PM:
---------------------------------------------------------------

[~mduerig]

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
in
[OAK-1855-r3|https://github.com/davidegiannella/jackrabbit-oak/commit/b110680ebc4a99317c12e7c481272800a2ee618a]
and you can see the output of the related build at
https://travis-ci.org/davidegiannella/jackrabbit-oak/builds/31710931
(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
fixtures

{{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;
where tests are FixturesHelper compliant.




was (Author: edivad):
[~mduerig]

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
in
[OAK-1855-r3|https://github.com/davidegiannella/jackrabbit-oak/commit/b110680ebc4a99317c12e7c481272800a2ee618a]
and you can see the output of the related build at
https://travis-ci.org/davidegiannella/jackrabbit-oak/builds/31710931
(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
fixtures

{{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
(v6.2#6252)