[
https://issues.apache.org/jira/browse/METRON-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282303#comment-16282303
]
ASF GitHub Bot commented on METRON-1344:
----------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/858
Point taken on maintaining 2 different solutions. Which services would
people want to enable remote debugging on? I've only ever debugged Metron code
so I don't know which services are important to people or why you would need to
put breakpoints in core service code. Enabling remote debugging will likely be
a little bit different for each service since each project has their own
mechanism for adding extra jvm params. I'm happy to do a POC for this once I
understand which services are important.
@ottobackwards I usually just leave mine running but spinning it up/down is
really fast once all the images are loaded.
> 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)
