All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST] Add a weekly coverity flight
Date: Mon, 4 Jan 2016 16:55:47 +0000	[thread overview]
Message-ID: <568AA413.2030605@citrix.com> (raw)
In-Reply-To: <22154.41506.565155.275702@mariner.uk.xensource.com>

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@xen.org 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@xen.org
>> +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

  reply	other threads:[~2016-01-04 16:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 11:45 [PATCH OSSTEST] Add a weekly coverity flight Ian Campbell
2016-01-04 16:47 ` Ian Jackson
2016-01-04 16:55   ` Andrew Cooper [this message]
2016-01-05 12:19   ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=568AA413.2030605@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.