[jira] [Commented] (SAMZA-386) Use Travis for continuous integration

["Jakob Homan (JIRA)" <ji...@apache.org>]

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

Jakob Homan commented on SAMZA-386:
-----------------------------------

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.  So it may still be worth looking at the Jenkins for patching testing and Travis for longer, post-commit integration tests.

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