[
https://issues.apache.org/jira/browse/METRON-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281947#comment-16281947
]
ASF GitHub Bot commented on METRON-1344:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/858
I agree with @cestella (and this might spill over into a discuss thread as
@ottobackwards mentioned). Maintaining both anything over other than short,
short term is going to be a nightmare. Invariably one or the other is going to
break independently of the other.
Assuming we do go with remote debugging of Docker (and that's a total
assumption, to be clear), we should make sure that the instructions aren't
IntelliJ dependent. Or at least, there are best effort instructions for people
using something else. I.e. if we end up using something like JetBrains' Docker
Integration plugin, I personally think we should have at least some debugging
instructions available outside that.
> 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)
