[jira] [Commented] (SAMZA-205) Bring Hello Samza in as an integration test

["Fred Ji (JIRA)" <ji...@apache.org>]

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

Fred Ji commented on SAMZA-205:
-------------------------------

I am considering breaking the  task of this JIRA into 4 steps:
 # Move hello-samza repo to samza-samples directory of samza repo;
 # Update the documentation related hello-samza to use the code in samza/samza-samples;
 # Deleted hello-samza repo;
 # build a gradle target such as samzaSampleIntegrationTests to hook the tests in samza/samza-samples;

> Bring Hello Samza in as an integration test
> -------------------------------------------
>
>                 Key: SAMZA-205
>                 URL: https://issues.apache.org/jira/browse/SAMZA-205
>             Project: Samza
>          Issue Type: Task
>          Components: hello-samza, test
>            Reporter: Jakob Homan
>            Assignee: Steve Yates
>            Priority: Major
>
> Hello Samza has proven to be a good integration test - ie, we break it on a regular basis - but we don't realize it until someone manually runs HS against the latest jars.  It would be better to have a gradle task that checks out the code, replaces the jars, tries to start up and runs for a bit.  
> Because HS requires internet access, we shouldn't have this run every time, but just as an extra step committers can use before actually checking in code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)