Further Coverity info

[Scott Ritchie]

On 4/9/13 7:34 AM, Allan LeSage wrote:
> * As part of our Jenkins CI program, we're Coverity-scanning merge
> proposals, and disapproving them upon finding a new defect:
> https://code.launchpad.net/~mrazik/unico/coverity/+merge/156877 .

As an upstream (wine) that uses Coverity, I'm curious how we can get 
this sort of feature in the free tier.  From what I can tell Coverity 
just periodically scans our git tree periodically and produces a list of 
reports.

We have a testbot that scans incoming patches (submitted via mailing 
list) to measure new defects: in Wine's case this is defined as tests 
that fail on one of the bot VMs, but if I could invoke coverity directly 
it could in principle scan an arbitrary patchset.

Do I need to setup some elaborate system of making a new git branch with 
the incoming patch set and then automatically asking coverity to scan 
that branch?  Or can it be manually invoked with arbitrary patches?