[
https://issues.apache.org/jira/browse/METRON-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otto Fowler updated METRON-857:
-------------------------------
Description:
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.
was:
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
> 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
> Assignee: 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)
