[
https://issues.apache.org/jira/browse/SAMZA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110948#comment-14110948
]
Yan Fang commented on SAMZA-386:
--------------------------------
am wondering if it is a good idea to send the Travis to the whole dev list? I
know, dev list is supposed to receive the "dev" information, but since we do
not have another "user" mailing list which is for general users, sending Travis
information to the whole dev list may distract the general users. Maybe only
sending to a few of us who cares about the build will be better?
> 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
> Assignee: Jakob Homan
> Fix For: 0.8.0
>
> Attachments: SAMZA-386-2.patch, 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)
