[
https://issues.apache.org/jira/browse/SAMZA-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181426#comment-15181426
]
Yi Pan (Data Infrastructure) commented on SAMZA-205:
----------------------------------------------------
[~yatessb], sorry to chime in late. I would think that if we bring in hs as an
integration test, the main purpose is to test that every check-in to Samza
master branch would work well w/ Hello-Samza latest branch. I think that it
would be easier to first support the trunk head development issue. As part of
the release process, we need to merge latest to master branch and validate hs
works. But we can have a separate solution to support release validation, which
should validate Hello-Samza master branch w/ a released branch in Samza.
> 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
>
> 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
(v6.3.4#6332)
