Re: [DISCUSS] Build RPM/DEBs in Travis?

You mean Otto thought of this already only 2 years ago? :) Skimming over that Jira thread, I think we're just looking for a pass/fail on the RPM/DEB builds at this point. I can't think of a reason why we'd need to bring Jenkins into it now that we have the ability to run multiple build sub-jobs

Re: [DISCUSS] Parser Aggregation in Management UI

Tibor, that sounds reasonable to me. If PR #1 ends up requiring code changes, will you guys just percolate those up through the remaining k PRs in order, or just the final PR? I'm wondering how this works in reference to your last point in #5 about rebasing. On Wed, May 22, 2019 at 8:47 AM Tibor

Re: [DISCUSS] Build RPM/DEBs in Travis?

https://issues.apache.org/jira/browse/METRON-885 On May 22, 2019 at 10:43:22, Justin Leet (justinjl...@gmail.com) wrote: Yep, that's all I was doing. I'm in favor of adding it to Travis. On Wed, May 22, 2019 at 10:28 AM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > I think Justin

Re: [DISCUSS] Parser Aggregation in Management UI

I would like to describe quickly *our approach to breaking down Parser Aggregation PR for smaller chunks* *1. we squashed the commits in the original development branch* - when we started to open smaller PRs from the commits from the original branch, we found ourself opening PRs out of historical

Re: [DISCUSS] Build RPM/DEBs in Travis?

Yep, that's all I was doing. I'm in favor of adding it to Travis. On Wed, May 22, 2019 at 10:28 AM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > I think Justin was just giving rationale, not suggesting we shouldn't make > the improvements. I think at one point we also had some

Re: [DISCUSS] Build RPM/DEBs in Travis?

I think Justin was just giving rationale, not suggesting we shouldn't make the improvements. I think at one point we also had some ambiguity about whether or how Docker was going to run in Travis, but I believe some folks have found a path through that? I agree with you both - let's get this added

Re: [DISCUSS] Build RPM/DEBs in Travis?

Yes, running up Full Dev is a manual verification that is required. And as a manual verification sometimes that will get missed. And in this specific case, tt does seem a bit silly that the addition of a parser should require the contributor to run up Full Dev. That being said, anything we can

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 >

Re: [DISCUSS] Build RPM/DEBs in Travis?

Theoretically, we didn't need to before there were both RPMs and DEBs since running dev up (which necessitates building those) is part of the build process. Since they've been split apart, I agree we probably should be building them, because nobody is going to run both unless they specifically

[DISCUSS] Build RPM/DEBs in Travis?

In light of issues like this https://github.com/apache/metron/pull/1419, has anyone looked into building our RPMs and DEBs in Travis? This is a very common and easy mistake to make and our CI builds really should be able to catch this.

[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

Re: Build Failed for 0.7.2

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 like this to one list, not to add them to random JIRAs. Simon On Wed, 22 May 2019 at 06:41, Farrukh Naveed Anjum wrote: > Requires: