On 09/12/2018 03:44 AM, Aurelien Bompard wrote: >> I like the CI test idea, a little bit like when we tests that the code base is pep8 compliant or the test coverage in above 90%. There are a couple of python packages that could be useful to help with that [0] [1]. >> >> [0] https://github.com/dhatim/python-license-check >> [1] https://github.com/raimon49/pip-licenses > > Pretty cool, I've implemented python-license-check for > fedora-messaging, it's quite trivial: > https://github.com/fedora-infra/fedora-messaging/pull/68 Nice! I like this idea too... it means the issue will be found closer to the upstream app, so it can be fixed quicker than if it got merged, released, and pushed into openshift. We just need to make sure all the apps we deploy that use pip/s2i use this method. kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
