[
https://issues.apache.org/jira/browse/METRON-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899602#comment-15899602
]
ASF GitHub Bot commented on METRON-671:
---------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/436
If someone is doing what the old workflow is ( just from the command line -
not opening ambari until everything is done ) they will never see anything but
the fail, please fix and try again. I don't think we should have this be a
'two parter', where the caller has to go hunting through different things in
the vm and out of it to hunt things down. The cadillac fix would be for a
post build step that gathers the logs into a buildResult dir or something. The
maven output that is 'eaten', the *.txt files that the ambari ui refers to.
Also, if someone wanted to use automation with this, it will be a problem.
There is, to me, a change with this, from a modular build where we were
doing multiple build steps, with each in and of itself being self documenting,
to a monolithic build
> Refactor existing Ansible deployment to use Ambari MPack
> --------------------------------------------------------
>
> Key: METRON-671
> URL: https://issues.apache.org/jira/browse/METRON-671
> Project: Metron
> Issue Type: Bug
> Reporter: David M. Lyle
> Assignee: David M. Lyle
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
