[
https://issues.apache.org/jira/browse/METRON-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281922#comment-16281922
]
ASF GitHub Bot commented on METRON-1344:
----------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/858
No matter what approach we take, my point is that we need to have some
thing that says you need to run docker to debug the tests. Beyond that, we
don't have to over back this. I think the approach in this pr is preferable to
the in-memory components in separate processes.
> 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)
