[
https://issues.apache.org/jira/browse/METRON-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923579#comment-16923579
]
Michael Miklavcic commented on METRON-2247:
-------------------------------------------
Can you verify all of what rpmlint checks for us? It's possible that we might
not need it by default at all when you consider a normal fulldev workflow, i.e.
spin up full dev to verify your changes haven't broken anything with the RPMs.
If successfully spinning up full dev with data flowing e2e effectively confirms
that the RPMs are in spec, then that step is redundant. I would still want the
option as a spot check, as needed.
> 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)
