Re: [Xen-devel] [PATCH] scripts: Add a script to build and submit to coverity.

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

On 10/12/15 17:48, Ian Jackson wrote:
> Andrew Cooper writes ("Re: [PATCH] scripts: Add a script to build and submit 
> to coverity."):
>> On 10/12/15 16:53, Ian Campbell wrote:
>>> ijc: Maybe we can think of a way to add this to osstest while still
>>> keeping the coverity token private?
>> This would be ideal.
> It doesn't sound particularly hard, apart from this wrinkle.
>
>>> +# Set $COV_EMAIL and $COV_TOKEN to credentials, otherwise it will
> ...
>>> +    declare -a curl_args
>>> +    curl_args+=("--form" "token=$COV_TOKEN")
>>> +    curl_args+=("--form" "email=$COV_EMAIL")
>>> +    curl_args+=("--form" "file=@$COV_TARBALL")
>>> +    curl_args+=("--form" "version=$COV_VERSION")
>>> +    curl_args+=("--form" "description=$COV_HEAD")
>>> +    curl_args+=("https://scan.coverity.com/builds?project=XenProject";)
> Is there a way to do this that does not involve the authentication
> token being passed on curl's command line ?
>
> Ideally there would be a way to get it to read the token from a file
> in $HOME.  We could then provide the token in ~osstest in the
> production colo.

One way or another, the authentication token needs to be in a post
header.  How this script and `curl` make it happen is open to improvement.

Perhaps something like this? (Completely untested)

--form token=@~osstest/coverity-secret-token

~Andrew

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