[
https://issues.apache.org/jira/browse/SAMZA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Homan updated SAMZA-386:
------------------------------
Attachment: SAMZA-386.patch
Attaching patch to bring in Travis CI. If committed, we'll need Infra to turn
on the Travis support for Samza (ala INFRA-6161). We'll also need to whitelist
the emails from Travis to dev.
A couple points:
* The Travis builds are limited to 3GB of memory total. For this reason I had
to turn down the heap on sama-kafka and samza-test to 2.5GB. The tests pass
with this limit, but I'm not sure if we'll see intermittent failures.
* The Travis build and configuration is very easy and supports multiple
configurations, similar to our check-all script. The nice thing about Travis
is that all the possible configurations run in parallel, so instead of 30
minutes, failure can be spotted in five or so.
* The artifacts from the build are not saved, so I ramped up the warning and
logging in the gradle output for failed tests to the max. I personally like
this better in general; it's closer to what Maven does. Test failures have
their stack traces inlined into the test output. If others don't like this, we
can have it be a setting that's just applied on the travis runs.
I've been testing this here:
https://travis-ci.org/jghoman/incubator-samza/builds
> Use Travis for continuous integration
> -------------------------------------
>
> Key: SAMZA-386
> URL: https://issues.apache.org/jira/browse/SAMZA-386
> Project: Samza
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.7.0
> Reporter: Jakob Homan
> Fix For: 0.8.0
>
> Attachments: SAMZA-386.patch
>
>
> We've looked at using ASF's Jenkins for a CI server before, but it appears
> unreliable. Some projects are now using Travis via the mirroring of ASF
> projects to github. We should take a look.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
