[
https://issues.apache.org/jira/browse/METRON-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281167#comment-16281167
]
ASF GitHub Bot commented on METRON-1344:
----------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/858
Doesn't necessarily have to be Docker but yes you would have to start
something up. That step is now outside of the integration tests.
We could keep the current in memory code and offer a debug mode. Is there
a benefit to using an in-memory component when debugging?
> Externalize the infrastructural components using integration tests
> ------------------------------------------------------------------
>
> Key: METRON-1344
> URL: https://issues.apache.org/jira/browse/METRON-1344
> Project: Metron
> Issue Type: Improvement
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
>
> As we move towards adding the Alerts UI e2e test to our continuous build, we
> need to remove the dependence on vagrant full dev and provide equivalent
> infrastructure within Travis. This will include all the services that the
> e2e tests depend on including Kafka, Zookeeper, Elasticsearch (possibly
> HBase), and Metron REST.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
