metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Allen <>
Subject Re: CI Builds
Date Mon, 21 Mar 2016 13:41:05 GMT
Ah, yes.  That work looks good, although a few other things have changed
since then.  We need to (1) add the apache-rat license check (2) execute
the 'integration-test' target.

Would you be willing to update that PR or submit a new one?  If so, I will
try and shepard in your changes.

On Mon, Mar 21, 2016 at 9:30 AM, Elana Hashman <>

> Paul and I worked on this two months ago but it never got merged:
>  I'd like to get automated CI builds working for the project.  It seems
> that Travis CI ( is quite popular and integrates
> well
> with Github.  I would certainly be open to alternatives though.
> I set Travis up on my own project fork just to understand how it might
> work.  If you follow the link, you will see that I added a badge to the top
> of the main project This badge displays the current CI build
> status.  It is updated each time a CI build completes.
> Travis will also auto-magically run a CI build for any PR that is opened.
> I think this is an outstanding feature so we have some additional
> validation before we merge anything into master.  Follow the link below to
> see an example PR.
> I had to create a .travis.yml file in the project root.  This tells the CI
> build to run the Apache Rat license check, runs the integration tests, and
> also packages the project.
> The only trouble I had was that Travis limits the output of CI builds to 4
> mb.  Beyond that it fails the build.  That is why you will see a bit of
> grep filtering in the Travis yml.
> Are you in favor of an automated CI build?  Is Travis CI the best
> solution?  All feedback welcome.
> Thanks
> Nick

Nick Allen <>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message