You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@metron.apache.org by "Dale Richardson (Jira)" <ji...@apache.org> on 2019/09/05 01:48:00 UTC

[jira] [Assigned] (METRON-2247) rpm-docker: Provide an option to bypass running rpmlint

     [ https://issues.apache.org/jira/browse/METRON-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dale Richardson reassigned METRON-2247:
---------------------------------------

    Assignee: Dale Richardson

> rpm-docker: Provide an option to bypass running rpmlint
> -------------------------------------------------------
>
>                 Key: METRON-2247
>                 URL: https://issues.apache.org/jira/browse/METRON-2247
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Dale Richardson
>            Assignee: Dale Richardson
>            Priority: Minor
>
> I notice that a large chunk of the time that an rpmbuild process takes is spent running rpmlint.  For people using the full dev process to spin up a Metron cluster, running rpmlint is like running unit-testing - the assumption is that the author of the code you are running has already done these tests.
> I propose that running rpmlint should remain as part of a full dev build, but that it would be useful to provide an argument that you pass to vagrant that will cause the running of rpmlint to be skipped.  This could speed up the process of standing up a full dev cluster for those people who want it.
>  



--
This message was sent by Atlassian Jira
(v8.3.2#803003)