[
https://issues.apache.org/jira/browse/METRON-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15979908#comment-15979908
]
ASF GitHub Bot commented on METRON-857:
---------------------------------------
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/543#discussion_r112808990
--- Diff: metron-deployment/packaging/docker/ansible-docker/Dockerfile ---
@@ -21,10 +21,10 @@ RUN yum install -y tar
RUN yum install -y wget
RUN yum groupinstall -y "Development tools"
RUN yum install -y zlib-dev openssl-devel sqlite-devel bzip2-devel
libffi-devel
-RUN wget https://www.python.org/ftp/python/2.7.10/Python-2.7.10.tgz -O
/usr/src/Python-2.7.10.tgz
+RUN wget https://www.python.org/ftp/python/2.7.12/Python-2.7.12.tgz -O
/usr/src/Python-2.7.12.tgz
--- End diff --
Sure, let me 2x check that
> 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)
