Uploaded image for project: 'csit'
  1. csit
  2. CSIT-1058

Usability: Make it easier for contributors to check code style

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Low Low
    • Release 19.04.1
    • None
    • None

      Currently, we have verify jobs which perform various style checks. For example, csit-validate-pylint-master job uses "pylint" to check style of Python resources. But parts of its configuration (pylint==1.5.4) and the command to execute are currently defined in ci-management repository, making local verification it less obvious.

      First step is to add the pylint version into CSIT root requirements.txt, and put the command into a script (also in CSIT git repo) which can be called reasonably simply by both the jenkins job and local contributor (assuming virtualenv has been activated and similar).

      Long-term improvement will be to migrate to "tox", which handles the virtualenv and dependencies automatically, and can combine multiple style checkers.

            vrpolak Vratko Polak
            vrpolak Vratko Polak
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: