I am not too familiar with the methods they use, but I believe they try and split up tasks based on the dependency tree. There are known issues though. To your point it won't be as simple as just switching travis' build config. If build times become an issue, it may be worth the investigation. Here is a link to a description of how it works ( https://cwiki.apache.org/confluence/display/MAVEN/Parallel+builds+in+Maven+3 ).
On Tue, Jan 17, 2017 at 8:58 AM, Michael Miklavcic < michael.miklav...@gmail.com> wrote: > How does Maven split tasks up these tasks? My only concern there is that we > have some robust integration test infrastructure data setup that may not be > thread-safe. > > On Tue, Jan 17, 2017 at 7:55 AM, jjmeyer0 <g...@git.apache.org> wrote: > > > Github user jjmeyer0 commented on the issue: > > > > https://github.com/apache/incubator-metron/pull/418 > > > > If time outs are going to continue being an issue, maybe we should > > start looking into using Maven's parallel builds. For example, when I > build > > locally I always do: `mvn -T 2C clean package`. This means build using 2 > > threads per core. It usually cuts the build time in half for me. > > > > > > --- > > If your project is set up for it, you can reply to this email and have > your > > reply appear on GitHub as well. If your project does not have this > feature > > enabled and wishes so, or if the feature is enabled but not working, > please > > contact infrastructure at infrastruct...@apache.org or file a JIRA > ticket > > with INFRA. > > --- > > >
