[
https://issues.apache.org/jira/browse/SAMZA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101575#comment-14101575
]
Jakob Homan commented on SAMZA-386:
-----------------------------------
bq. IMO, this is a pretty big draw back. I really like the CI jobs running on
patch submit like they do in Hadoop-land.
Travis can do pre-commit checks on github pull requests, but I since they're so
connected to github, I doubt they're spending many cycles on integrating with
JIRA.
bq. (1) how unstable is Hudson going to be for us
I'll see if I can get some cycles on this before I go back in the thick o
fthings
bq. (2) does ASF have any plans to integrate the "submit patch" test feature
with Travis?
Assuming we wanted to try using pull requests again, it would work. But that
was pretty painful. I see this as a good supplement to Jenkins, at least until
either Jenkins works for everything we need and/or we decide to go pull-request
route.
bq. Is it possible to have Travis email the dev list, or commits
The patch currently has this enabled for dev. It will use Travis' default
which is to email on build failures and a single email when the build has
recovered. By default it doesn't email for each successful build, though
that's an option too and I set it for the IRC channel. We'll need to get the
Travis account whitelisted to dev.
Let's go ahead and try it and, if it's not useful, it's easy enough to remove.
It'll be nice to have all the Scalas and JDKs tested, even if we forget to when
committing (which I do pretty regularly).
[~criccomini], was your +1 on the patch? If so, I'll go ahead and commit it.
> 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)
