From 3d8526034af32c5c70929f6217aa8e5abeee59d5 Mon Sep 17 00:00:00 2001 From: Chris Leech Date: Wed, 23 Oct 2019 15:53:31 -0700 Subject: fix Coverity scan Here I thought I was all carefull about it before pushing the config. I guess a notification_email is required, I was hoping that could all be managed on the repo setting in Coverity. I'll put myself down. --- .travis.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to '.travis.yml') diff --git a/.travis.yml b/.travis.yml index c6aebda..f11db8b 100644 --- a/.travis.yml +++ b/.travis.yml @@ -5,6 +5,9 @@ dist: bionic env: global: + # This is an excrypted setting of COVERITY_SCAN_TOKEN= + # Travis-CI has the private key to decrypt this and set the environment + # variable with the token needed for Coverity API access - secure: kUIw3pil4akjNycH+R2mq8oUszQrt/TCwkQb20oBRXoqsRzYLF6I9VT5wdAERjPsD7BDSiWLxLnisYrdRAs/tQ9h3xvnOJQAX8wKvVF/B883kOwOdI17DkY/dKdzWT+LbojjaXCHZf2yaKVAjibRPO2E8J9zsvpuDLDlon7zD123Amnb/XrSVJH4jefscs1OXFVtaMIKNs7AQPoPK7V9oMZoIbBF5NhYSPpytlf5/VL6ePQlXdd4xAiQR+dg5PvEbMquJh4GvcTo5DzOAJN8L9nGvlGlH5YKxHo7tkOpKFRnCATyenbpVaUBTb/TzA9OsVmxfSr/WrzLLXQxCwfOG6ktZp+1+ANRuL5wLCtDJLooGCw4Wxsicgw69snBoFPWoPW8w4osNQAaGINZnPKM2WSFxq2DBrqHrccGk1lze7upNHikBrwSTgv+SklmZUfcDQjWYxC2owH21BHhVTV6hgNShwS5q9gwWtSWAHc4f34Qvn1gjdV2/791Skk/t4GgTSmt0j0ZVcfsQJaZBvDwkot1yDJ0u/3av+ElMAmCb/9wG3dSqUXv9/V6mAutNb243igIZko6Vmpcosp2bJKXyeVbRkgbMoIfH2VQf9n1sbb01+V9lZsk9usIZZYRcW9Bz6d2H+ooDrM/ha1kQjVqMDP2EyCdBKmQjr8iAi9E4yQ= addons: @@ -21,9 +24,10 @@ addons: coverity_scan: project: name: open-iscsi/open-iscsi + notification_email: cleech@redhat.com build_command: make branch_pattern: coverity_scan before_install: echo -n | openssl s_client -connect scan.coverity.com:443 | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' | sudo tee -a /etc/ssl/certs/ca- -script: if [ "{COVERITY_SCAN_BRANCH}" != 1 ]; then make; fi +script: if [ "${COVERITY_SCAN_BRANCH}" != 1 ]; then make; fi -- cgit v1.2.1