[
https://issues.apache.org/jira/browse/OAK-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080849#comment-14080849
]
Davide Giannella edited comment on OAK-1855 at 7/31/14 3:44 PM:
----------------------------------------------------------------
*RTC*
Managed to have the build running and completing in a decent time.
https://travis-ci.org/davidegiannella/jackrabbit-oak/builds/31327009
As it's a crucial part of our development I'd ask to review what I did
before committing.
https://github.com/davidegiannella/jackrabbit-oak/commit/51d4f3530352548a78eb229d76f6a2bcacb242cc
*In a nutshell*
Split the build into 4 different profiles: pedantic, unittesting, IT
over Segment and IT over all Documents.
This is done by using the env variable {{ns-fixtures}}. See
[FixturesHelper|https://github.com/davidegiannella/jackrabbit-oak/commit/51d4f3530352548a78eb229d76f6a2bcacb242cc#diff-fed97835e439cc5cc599dad06d08092bR1].
When running locally {{mvn clean install}} it will run the TCK and
AbstractRepository tests against Segment. It's easy to override in
case with
{noformat}
mvn clean install -Dns-fixtures=DOCUMENT_NS
# you can leave it blank and will run against all fixtures
{noformat}
unittesting profiles runs against all fixtures.
Disabled unit testing for the integration testing profiles and
pedantic ones.
If needed it's possible to have tests fixture aware. See
{{AbstractRepositoryTest}}, {{TCKBase}} and
{{OrderedIndexConcurrentClusterIT}} in the above commit for example.
{{integrationTesting}} profile now runs only on Segment and skip unit testing.
*We probably have to change something either here or in the release process*
was (Author: edivad):
*RTC*
Managed to have the build running and completing in a decent time.
https://travis-ci.org/davidegiannella/jackrabbit-oak/builds/31327009
As it's a crucial part of our development I'd ask to review what I did
before committing.
https://github.com/davidegiannella/jackrabbit-oak/commit/51d4f3530352548a78eb229d76f6a2bcacb242cc
*In a nutshell*
Split the build into 4 different profiles: pedantic, unittesting, IT
over Segment and IT over all Documents.
This is done by using the env variable {{ns-fixtures}}. See
[FixturesHelper|https://github.com/davidegiannella/jackrabbit-oak/commit/51d4f3530352548a78eb229d76f6a2bcacb242cc#diff-fed97835e439cc5cc599dad06d08092bR1].
When running locally {{mvn clean install}} it will run the TCK and
AbstractRepository tests against Segment. It's easy to override in
case with
{noformat}
mvn clean install -Dns-fixtures=DOCUMENT_NS
# you can leave it blank and will run against all fixtures
{noformat}
unittesting profiles runs against all fixtures.
Disabled unit testing for the integration testing profiles and
pedantic ones.
If needed it's possible to have tests fixture aware. See
{{AbstractRepositoryTest}}, {{TCKBase}} and
{{OrderedIndexConcurrentClusterIT}} in the above commit for example.
> 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)
