Currently pylint scans cause a build failure only if there are any errors or warnings in the code. All the conventions and refactoring issues are written to a file pylint-report in packages folder. It is required to investigate and fix these issues which improve the code. It can also be discussed if the build must fails if any of these types of issues show up.
master: dfe55982eb50750fc1e65bce312d884b1604f0b4
There are still other convention and refactoring warnings. This ticket should remain open until all warnings are fixed.
Metadata Update from @kaskahn: - Issue set to the milestone: UNTRIAGED
Currently all Python code is checked with pylint and flake8 via CI before commit. All remaining warnings that cannot be fixed right now are explicitly waived.
Metadata Update from @edewata: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: fixed - Issue set to the milestone: 10.6.0 (was: UNTRIAGED) - Issue status updated to: Closed (was: Open)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1272
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.