Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce code analysis #138

Open
shaun-edwards opened this issue Mar 7, 2017 · 4 comments
Open

Introduce code analysis #138

shaun-edwards opened this issue Mar 7, 2017 · 4 comments

Comments

@shaun-edwards
Copy link
Member

Does anybody have experience using sonar qube. It's a free code analysis service for open source projects. It looks like it integrates nicely with travis jobs as well.

@130s
Copy link
Member

130s commented Mar 8, 2017

I'm definitely interested in integrating something like sonar qube. This ticket can be labeled as enhancement. Related #98 #112

If anyone can start working please assign yourself or just claim here.

@mathias-luedtke
Copy link
Member

According to the travis docs it is just a matter of setting up the authentication and simply run sonar-scanner. For this kind of use cases we just need to implement the test branching as pointed out in the roadmap.

It should work like specifying TEST=sonarqube which results in invoking the corresponding sonarqube.sh from the tests folder. We could even try to find a matching script in the target repository.

@moriarty
Copy link

+1 for this.

I was introduced to Sonarqube when I joined a company over a year ago, and it's great.
I've brought it back to the university, where I was TA-ing a course, and had the students set up their own travis + sonar + github-sonar-plugin to automate as much of low level the review of their group projects... ( https://github.com/HBRS-MAAS/project )

It is easy to set up, if you're using python or java and a supported build system, either sonar cloud or the sonar docker image. I did have it running for PCL but it took a little more work for C++ you have to specify the include directories in the sonar.properties file.
https://github.com/SonarOpenCommunity/sonar-cxx/wiki/Code-checkers

That said, I haven't used it in combination with any ROS projects...
Which is why Google search brought me to this issue.

@mathias-luedtke
Copy link
Member

support for clang-tidy will be added in #402

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants