[
https://issues.apache.org/jira/browse/SUREFIRE-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16524959#comment-16524959
]
Enrico Olivelli commented on SUREFIRE-1529:
-------------------------------------------
I am not sure this is a good way to address the problem.
In my experience it is better to create sub maven mudules, maybe with
intermediate reactors.
Alternatively you can use junit Categories and use the -Dgroups options.
This will make builds always reproducible and you will have full control of
what is happening
> Implement test bucketing
> ------------------------
>
> Key: SUREFIRE-1529
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1529
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
> Affects Versions: 2.22.0
> Reporter: Zsombor Gegesy
> Priority: Major
> Attachments: SUREFIRE-1529.patch
>
>
> There are projects, which has hundreds or thousands of test, which took hours
> to complete - to paralelize this, it would be good, if tests could be
> partitioned automatically into buckets - of course perfect bucketization is
> not feasible, due to lack of knowledge of test run times (and it would be a
> NP-complete problem even that case).
> The idea is to start tests concurrently, in different machines, something
> like this:
> # mvn test -DnumberOfBuckets=3 -DbucketId=0
> # mvn test -DnumberOfBuckets=3 -DbucketId=1
> # mvn test -DnumberOfBuckets=3 -DbucketId=2
> And the results could be collected and aggregated later by external
> processes.
> The current solution is to manually collect the tests, and generate huge
> command lines to do the same.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
