[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

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-

This file needs a DEPLOYMENT NOTE I think.

The rest of this looks OK.  A review from Andrew Cooper might be
worthwhile ?


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.