Easier way exists. This patch should be dropped.

On 18 January 2017 at 13:34, Christophe Milard
<christophe.mil...@linaro.org> wrote:
> On 18 January 2017 at 13:26, Maxim Uvarov <maxim.uva...@linaro.org> wrote:
>> On 01/18/17 16:14, Christophe Milard wrote:
>>> Signed-off-by: Christophe Milard <christophe.mil...@linaro.org>
>>> ---
>>>  .travis.yml | 18 ++++++++++++++++++
>>>  1 file changed, 18 insertions(+)
>>>
>>> diff --git a/.travis.yml b/.travis.yml
>>> index 03e61b1..909f0a3 100644
>>> --- a/.travis.yml
>>> +++ b/.travis.yml
>>> @@ -6,11 +6,29 @@
>>>  # pushing to github/master will run make check
>>>  # pushing to github/coverity_scan will also launch a static analysis
>>>  # See https://scan.coverity.com/travis_ci
>>> +# Note: "push -f" seems to have problems, do not rely on it to trigger CI 
>>> from
>>> +# github (push new commits, without '-f').
>>>
>>>  env:
>>>    global:
>>>      # COVERITY_SCAN_TOKEN
>>>      # ** specific to your project **
>>> +    # Note:
>>> +    # You should have a github account and travis linked travis account.
>>> +    # To generate the proper encrypted token you need to install ruby-dev
>>> +    # and gem_install travis as follows:
>>> +    # % sudo apt-get install ruby-dev
>>> +    # % sudo gem install travis
>>> +    # then run:
>>> +    # % travis encrypt  -r <you>/<proj> encrypt COVERITY_SCAN_TOKEN=<token>
>>> +    # where <you> is your github login
>>> +    # where <proj> is your github repo, e.g. "odp"
>>> +    # where <token> is the "Project Token" found on the coverity web page:
>>> +    # https://scan.coverity.com/dashboard -> <you>/<proj> -> 
>>> Project_settings
>>> +    # e.g.:
>>> +    # % travis encrypt  -r christophe/odp encrypt  
>>> COVERITY_SCAN_TOKEN="v-HOHTCHPkya4cx2cscrYg"
>>> +    # The output string, about 700 characters long, should replace xxxx 
>>> below.
>>> +    #
>>>      - secure: "xxxx"
>>>
>>>  language: c
>>>
>>
>>
>> I did not do all that things. I just copy-pasted token from web page.
>> Also there is button to generate new if needed.
>
> ??? Did you find the 687 char encryptred token anywhere???
> Or did you just paste the normal short unencrypted token (length = 22 or so)?
> And you got coverity to go? not just the build?
>
> I did copy the TOKEN as found in the web page, but travis kept failing, with:
>
> "Coverity Scan API access denied. Check $PROJECT_NAME and 
> $COVERITY_SCAN_TOKEN."
>
> Confused.
>
> Christophe.
>
>>
>> Maxim.

Reply via email to