Re: Build Failed for 0.7.2

2019-05-23 Thread Farrukh Naveed Anjum
Thanks, Is it available in master ? On Wed, May 22, 2019 at 12:27 PM Simon Elliston Ball < si...@simonellistonball.com> wrote: > See https://github.com/apache/metron/pull/1419 which fixes this issue and > will likely make it to master pretty soon. > > FYI: probably only necessary to post things

Re: [DISCUSS] Travis CI Build Time Limits

2019-05-23 Thread Nick Allen
> (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

2019-05-23 Thread Justin Leet
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

2019-05-23 Thread Otto Fowler
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

2019-05-23 Thread Michael Miklavcic
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

2019-05-23 Thread Michael Miklavcic
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] Parser Aggregation in Management UI

2019-05-23 Thread Tibor Meller
Yes, am expecting that some change request will rase due to the review. We planning to add the changes to the latest PR as additional commits to avoid impacting the PR sequence. We will refer to the source PR in the commit message of the fix. Also adding a link to the comment section of the source