[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: Xen FuSa meeting tomorrow Tue 17 November
Hi Stefano, On 18/11/2020 18:20, Stefano Stabellini wrote: On Wed, 18 Nov 2020, Julien Grall wrote:Hi Stefano, On 18/11/2020 17:43, Stefano Stabellini wrote: > If the commercial tool is available "as a service", and its services canbe invoked automatically from the headless Linux container in the CI-loop, that would work and might solve the issue of the licensing agreement. Note that Coverity is available "as a service" but I don't think it can be invoked automatically from a headless Linux container: typically a human needs to login the web interface to get the results.Xen Project Coverity is invoked from OSStest. We receive e-mail with the number of defects eliminated/found. For new issues, you will get a summary of each of them. If that not what you have in mind for headless Linux, then I am not sure what you are looking for.Ah, that's good, I wasn't aware of that about Coverity. I had in mind something more like a remote API, maybe a REST API. But getting an email back is OK too: we could fetch it and parse it automatically from the Linux container. I know that my team has coverity integrated so we get: - ticket cut on new defects- a bot commenting on pending code review with defects introduced/removed. It is even capable to comment on the line introducing the defect. So you have enough data from coverity to provide some meaningful information. :) I don't know whether this is based on just parsing e-mails or tools coverity may provide in a paid version. Cheers, -- Julien Grall
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |