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
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
