Add a possibility to run cppcheck on submitted patches

[GoogleCodeExporter]

It would be nice to have a possibility to run cppcheck (C++ static code 
analysis tool) on submitted patches on server side. It may be done in the next 
way: 1) run it on file before modification; 2) run it on file after 
modification; 3) compare results and warn if new errors/warnings appear. 
cppcheck can generate XML outputs, so I don't think it would be very hard to 
add error highlighting also (but text output will be good anyway)

Original issue reported on code.google.com by annu...@gmail.com on 6 Jul 2010 at 8:42

• Blocked on: #861

[GoogleCodeExporter]

Issue 619 has been merged into this issue.

Original comment by sop@google.com on 12 Jul 2010 at 9:03

[GoogleCodeExporter]

It sounds like what you might be looking for is a continuous integration server 
like Jenkins (http://jenkins-ci.org/) to run tests for you whenever someone 
commits to a repository.

Jenkins can be setup to talk to gerrit and mark commits as "Verified +1" or 
"Verified -1" automatically whenever a test succeeds/fails.

Original comment by francoisatwork@gmail.com on 12 Apr 2011 at 6:09

[GoogleCodeExporter]

Will be supported through plugin support.

Original comment by nas...@grainawi.org on 20 May 2011 at 9:57

• Changed state: Accepted

[GoogleCodeExporter]

This would be a FANTASTIC feature.

When working on old code in the hundred of man-years and tens of thousands of 
warnings, this would allow getting quality ratchet in place.

Once a warning is fixed, it will never creep back in...

Original comment by oyvindha...@gmail.com on 1 Oct 2013 at 1:59