Task #779

Updated by Spyhawk almost 5 years ago

We actually use "coverity":https://scan.coverity.com/projects/1160 as static analysis tool to improve quality of our codebase, and monitor the introduction of new bugs. According to the size of our current codebase, we're allowed to submit 2 scans/day max and 8 scans/week max.

Scans are actually triggered manually by myself about every each 1-2 days with "this script":http://dev.etlegacy.com/projects/etlegacy/wiki/Spyhawks_notes#Coverity-scan-script, but it might be wise to completely automate this task with a cron job on our server.

A scan requires pull the last code from git, run the script which will compile the code, create some files and send them to coverity for analysis.