ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
![]() | 1 | initial version |
In general we don't add code analyzers / linters to the buildfarm alone since it would make it difficult to reproduce the results locally.
Instead in ROS 2 any kind of linters are integrated on a per-package level. So when you run the tests of a package you also run any kind of linter available (e.g. clang-format
, clang-tidy
, cppcheck
, cpplint
, flake8
, uncrustify
, xmllint
). The generally used ones are in this repo: https://github.com/ament/ament_lint
For ROS 1 there is no such infrastructure for linters and you would need to integrate each linter manually into each package.
![]() | 2 | No.2 Revision |
In general we don't add code analyzers / linters to the buildfarm alone since it would make it difficult to reproduce the results locally.
Instead in ROS 2 any kind of linters are integrated on a per-package level. So when you run the tests of a package you also run any kind of linter available (e.g. clang-format
, clang-tidy
, cppcheck
, cpplint
, flake8
, uncrustify
, xmllint
). The generally used ones are in this repo: https://github.com/ament/ament_linthttps://github.com/ament/ament_lint All of these produce xUnit compliant result file to be picked up by Jenkins when running the tests in the buildfarm.
For ROS 1 there is no such infrastructure for linters and you would need to integrate each linter manually into each package.