[
https://issues.apache.org/jira/browse/SAMZA-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249926#comment-15249926
]
Steven Yates commented on SAMZA-205:
------------------------------------
Hi [~nickpan47] so far I have managed to introduce an additional task into then
gradle build process for samza which when run (i.e. gradle clean
testHelloSamzaIntegrationTest) actually checks out the master branch of the
Hello Samza repo or a specific branch if supplied as a parameter to the build
process i.e. helloSamzaVersion=LATEST etc .
Once this checks out within the current work space the idea was to somehow pass
through the appropriate SLF4J_VERSION, SAMZA_VERSION, KAFKA_VERSION and
HADOOP_VERSION to the HellSamza runWikiFeed task in order to run the HelloSamza
code base against the correct working version of above mentioned frameworks. By
default HelloSamza checks out said versions of frameworks from local maven repo
or mavenCentral if doesn't exist however it may be the case we are operating in
a branch and I have made a whole bunch of changes to SAMZA (most likely the
case) and I wish to test against a locally published snapshot of this code so I
was thinking of introducing a further version keyword into the HelloSamza
gradle code 'LOCAL" or some such word and some code to apply the correct
dependency set which would be the product of all the locally built jars in the
local samza dirs ../build/libs directory.
I may have over thought the whole process though mate so any suggestions /
feedback you have would be great.
Kind Regards
S
> 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)
