Re: [Xen-devel] [PATCH OSSTEST] Add a weekly coverity flight

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

On 04/01/16 16:47, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST] Add a weekly coverity flight"):
>> Move collectversions into Osstest::BuildSupport rather than
>> duplicating with ts-xen-build (nothing else is really duplicated)
> This could profitably be split into a separate patch IMO.
>
>> For the cr-* integration we treat branch=coverity as a special case of
>> tree=xen. I didn't think tree=coverity made much sense, and would
>> probably reach tendrils into lots of other places (such as the
>> invocations of check_tested).
>>
>> TODO: How to pick $c{CoverityEmail}, needs to be a real email which is
>> in coverity project (which security@xxxxxxx used here is not)
> I don't have an answer to this but perhaps osstest-admin@xenproject ?
> Or will it get lots of annoying output ?  (We could filter it to make
> it go to osstest-output I guess...)
>
>> +CoverityEmail security@xxxxxxx
>> +CoverityTools cov-analysis-linux64-7.7.0.4.tar.gz
> This file needs a DEPLOYMENT NOTE I think.
>
> The rest of this looks OK.  A review from Andrew Cooper might be
> worthwhile ?

I don't speak much perl, nor know the internals of OSSTest.

However, the snippets of shell for building look correct.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel