You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@metron.apache.org by "Nick Allen (Jira)" <ji...@apache.org> on 2019/10/01 20:42:00 UTC

[jira] [Updated] (METRON-2271) Reorganize Travis Build

     [ https://issues.apache.org/jira/browse/METRON-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Allen updated METRON-2271:
-------------------------------
    Description: 
The way in which we organize the Travis builds ensures that each job will build all of Metron, each time.  Although we attempt to cache the local Maven repository to avoid this, in practice all jobs start roughly in parallel and so this cache is never used.

We are increasingly hitting the 50 minute time limit on our integration test job which causes the Travis build to fail.  By reorganizing the build, so that each job only builds the modules that it needs, we should be able to save some time and avoid breaching this time limit.

 

> Reorganize Travis Build
> -----------------------
>
>                 Key: METRON-2271
>                 URL: https://issues.apache.org/jira/browse/METRON-2271
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Nick Allen
>            Assignee: Nick Allen
>            Priority: Major
>
> The way in which we organize the Travis builds ensures that each job will build all of Metron, each time.  Although we attempt to cache the local Maven repository to avoid this, in practice all jobs start roughly in parallel and so this cache is never used.
> We are increasingly hitting the 50 minute time limit on our integration test job which causes the Travis build to fail.  By reorganizing the build, so that each job only builds the modules that it needs, we should be able to save some time and avoid breaching this time limit.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)