[
https://issues.apache.org/jira/browse/METRON-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856835#comment-15856835
]
ASF GitHub Bot commented on METRON-705:
---------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/444
Looking at those logs, it appears that the first phase, the build (not the
actual integration tests) is 4 minutes 39 seconds in my integration-test phase
[build](https://api.travis-ci.org/jobs/199327334/log.txt?deansi=true) on travis
vs 21 minutes 53 seconds on
[yours](https://api.travis-ci.org/jobs/199370358/log.txt?deansi=true)
> Parallelize the build in travis to the extent that is obvious
> -------------------------------------------------------------
>
> Key: METRON-705
> URL: https://issues.apache.org/jira/browse/METRON-705
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
> Assignee: Casey Stella
>
> Travis suggests at
> https://blog.travis-ci.com/2012-11-28-speeding-up-your-tests-by-parallelizing-them/
> that for situations where the integration get chunky, we can parallelize
> them using their build matrix. Also, if we can separate those out, we can
> also process-parallelize the unit and build.
> This is just a stopgap that requires no code changes to lower build
> wall-clock times.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
