My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 618: Add a possibility to run cppcheck on submitted patches
8 people starred this issue and may be notified of changes. Back to list
Status:  Accepted
Owner:  ----

Blocked on:
issue 861


Sign in to add a comment
 
Reported by annu...@gmail.com, Jul 6, 2010
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)
Jul 12, 2010
#1 sop@google.com
 Issue 619  has been merged into this issue.
Apr 11, 2011
#2 francoisatwork@gmail.com
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.
May 20, 2011
Project Member #3 nas...@grainawi.org
Will be supported through plugin support.
Status: Accepted
Blockedon: 861
Oct 1, 2013
#4 oyvindha...@gmail.com
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...


Sign in to add a comment

Powered by Google Project Hosting