[
https://issues.apache.org/jira/browse/SAMZA-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091808#comment-15091808
]
Steven Yates commented on SAMZA-205:
------------------------------------
Hi [~jakobhoman], on second thoughts I believe it might be much easier to split
this into two tasks. We can create a task which uses a local Git installation
and checks out Hello Samza into the project structure, secondly if on
initialisation gradle detects the hello-samza project exists within it's
workspace it can include the hello-samza build.gradle and associated tasks.
Any thoughts?
> 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)
