[
https://issues.apache.org/jira/browse/METRON-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532006#comment-16532006
]
ASF GitHub Bot commented on METRON-1650:
----------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/1091
Point taken. The issue we have is that our builds take a long time so we
have to prioritize what is included in travis. There are several components
that can't be tested in travis even if we wanted to so we test with our VM
environment frequently (daily). That's the world we live in :)
This could be added to travis but I don't know that it's worth it because
this part of Metron (setting up a Docker container to build in) doesn't change
very often. Changes that modify our packages (adding/removing scripts or other
assets) need to be tested and demonstrated in full dev anyways. Others might
have a different opinion though.
> Packaging docker containers are too large
> -----------------------------------------
>
> Key: METRON-1650
> URL: https://issues.apache.org/jira/browse/METRON-1650
> Project: Metron
> Issue Type: Improvement
> Reporter: James Lamb
> Priority: Minor
>
> I have been looking through the project source code, and found that the
> packaging docker containers are bigger than they need to be.
> The containers' size could be cut substantially by:
> * Grouping as many commands as possible into as few RUN stages as possible
> * Taking advantage of `yum clean` and `apt-get clean`
> * Removing artifacts pulled with `wget`
> * Removing unused libraries or libraries only needed at build time (like
> `tar` and `wget`)
> I am creating this issue but will soon submit a PR to address it.
> Thank you for considering my proposal!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
