Re: [DISCUSS] Travis CI Build Time Limits

> (1) The build is really a tree of modules. With our recent de-coupling from Storm, this has become all the more exaggerated... I agree that the approach I followed in my POC suffers from the risk of a future refactor accidently causing some tests not to run. But I just did it this way

Re: [DISCUSS] Travis CI Build Time Limits

Yeah, it'd be a one time thing, but there's no guarantee our builds (including master) actually run after invalidating the caches. Unfortunately, I don't really have time in the immediate future to play around with it a whole lot to find out if it's viable without additional work (e.g. kick off

Re: [DISCUSS] Travis CI Build Time Limits

Yes, that is what I’m proposing, but if we want to try to break things down to speed them up, we can still do that ;) On May 23, 2019 at 11:28:51, Michael Miklavcic (michael.miklav...@gmail.com) wrote: I think we're talking about killing the cache just 1 time for the purpose of verifying that

Re: [DISCUSS] Travis CI Build Time Limits

I think this is a neat idea, however I have a couple concerns with this: 1. The build is really a tree of modules. With our recent de-coupling from Storm, this has become all the more exaggerated. This is a good thing, however the benefit of the parent pom approach we currently have is

Re: [DISCUSS] Travis CI Build Time Limits

I think we're talking about killing the cache just 1 time for the purpose of verifying that the https:// repo endpoints will work. It's possible I'm misunderstanding how we've configured our caches, but it seems like we'd just need to kick travis 1x after the first failed build that did all the

Re: [DISCUSS] Travis CI Build Time Limits

FYI - Here is a POC build of this concept running. This only runs the Parser and Enrichment integration tests, but as separate jobs in Travis. https://travis-ci.org/nickwallen/metron/builds/535791047 On Wed, May 22, 2019 at 9:20 AM Nick Allen wrote: > > > Justin Leet said >

[DISCUSS] Travis CI Build Time Limits

> Justin Leet said [1]: Looking at our build times, I'm actually concerned that if we kill the caches our builds won't complete. The integration tests take >45 minutes and it's very possible redownloading everything goes over our