[
https://issues.apache.org/jira/browse/METRON-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280404#comment-16280404
]
ASF GitHub Bot commented on METRON-1344:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/858
@merrimanr Did you look into what migrating our non-e2e tests integration
tests would involve? I think for a POC, it's important to get a sense of how
we'd be able to unify the infrastructure of these, even if they aren't
necessarily all unified at POC time. If not, are you planning on investigating
that once you resolve the current list of e2e issues?
> 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)
