[ 
https://issues.apache.org/jira/browse/SAMZA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100708#comment-14100708
 ] 

Chris Riccomini commented on SAMZA-386:
---------------------------------------

I personally don't have much experience with Tracis CI, but it looks pretty 
nice. I'm mostly just in favor of getting CI up and running. :) The IRC 
notification feature in the travis.yml is also really awesome looking.

bq. One other difference from the ASF Jenkins farm is that there we can run 
tests on patch submission, whereas with Travis they run after the patch is 
committed.

IMO, this is a pretty big draw back. I really like the CI jobs running on patch 
submit like they do in Hadoop-land. Still, I don't see this as a blocker. I 
guess the two questions I have are (1) how unstable is Hudson going to be for 
us, and (2) does ASF have any plans to integrate the "submit patch" test 
feature with Travis?

bq. 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.

Hmm, it might be OK. Those tunings were all done before SAMZA-245, so they 
could be off a bit. Also, some of those tunings were done not because things 
were failing, but because the TestSamzaContainerPerformance test was GC'ing a 
lot, which was slowing the test down, and making the results inaccurate.

All in all, I think I'm +1 on this.

> 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)

Reply via email to