[
https://issues.apache.org/jira/browse/METRON-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280785#comment-16280785
]
ASF GitHub Bot commented on METRON-1344:
----------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/858
Sorry @ottobackwards, you're right the instructions are a little vague.
First, `metron-contrib/metron-docker-e2e/compose` is the directory you should
be in. I should have added that at the beginning. Not all steps require you
be in that directory but steps 4 and 5 do.
So you can't run the tests in the same exact way now because the Alerts UI
host is hardcoded in the e2e tests (add that to our list of things to address).
It is hardcoded to "localhost" which works fine in travis but won't work in
Mac OSX because of networking limitations (Docker has to run in a vagrant
machine). Let me come up with a plan that will allow you to easily run the e2e
tests locally.
> 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)
