[
https://issues.apache.org/jira/browse/SAMZA-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073454#comment-15073454
]
Steven Yates commented on SAMZA-205:
------------------------------------
So I have done some research on this, how would the project feel if we
introduce a gradle git plugin to allow us to checkout the hello-samza project
into say the /build directory. The only way I can see this working without
bringing hs in as a git submodule would be to ;
1) create a custom task i.e. task runHelloSamzaIntegrationTest << {....}
2) have this task depend on the completion of build (so we have the local
binaries of the sub projects withing /build)
3) once hs has been cloned into say /build/hello-samza we could initialise the
wikiStats task with a samza version of LOCAL (or some equivalent)
4) based on this samza version input we can determine whether to use the
current repositories i.e. mavenCentral() or a FlatFileRepository i.e. the local
binaries.
That is my thinking to date on this. It's not as straight forward as I
originally thought it would be as you need to swap in a different set of deps
depending on the environment your intending to execute the hs tests in.
If you can think of a better way, please share.
> 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)
