[
https://issues.apache.org/jira/browse/METRON-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983230#comment-15983230
]
David M. Lyle commented on METRON-857:
--------------------------------------
I get a failure when running quick-dev after this was merged:
{code}
TASK [quick_dev : Re-install the Metron Packages via Ambari] *******************
failed: [node1] => (item=METRON_ENRICHMENT_MASTER) => {"failed": true, "item":
"METRON_ENRICHMENT_MASTER", "msg": "Request failed with status FAILED"}
failed: [node1] => (item=METRON_INDEXING) => {"failed": true, "item":
"METRON_INDEXING", "msg": "Request failed with status FAILED"}
failed: [node1] => (item=METRON_PARSERS) => {"failed": true, "item":
"METRON_PARSERS", "msg": "Request failed with status FAILED"}
PLAY RECAP *********************************************************************
node1 : ok=56 changed=10 unreachable=0 failed=1
{code}
If this is happening for others, can we please revert this until there's a fix?
> Metron should one unified docker build image
> --------------------------------------------
>
> Key: METRON-857
> URL: https://issues.apache.org/jira/browse/METRON-857
> Project: Metron
> Issue Type: Improvement
> Reporter: Otto Fowler
>
> Right now, we have a docker environment for building the code of the product,
> and a docker image for building rpms.
> If you are in an environment that requires the first, you cannot use the
> second from there.
> We should have a merged, unified metron build environment that builds the
> whole product.
> This will enable workflows such as:
> https://cwiki.apache.org/confluence/display/METRON/Metron+Installation+on+an+Ambari-Managed+Cluster
> That page can be updated once this is complete as well
> The approach:
> Using maven profiles and profile activation it is possible to have two
> versions of the exec call to build rpms, one that calls docker and one that
> just calls the script.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
