On Sat, Apr 20, 2019 at 10:55 AM Apache Jenkins Server < jenk...@builds.apache.org> wrote:
> See < > https://builds.apache.org/job/guacamole-client-coverity/104/display/redirect?page=changes > > > ... > + curl --data-urlencode token=[*******] --data-urlencode > project=guacamole-client https://scan.coverity.com/download/linux64 > + tar -xz > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- > 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- > --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- > --:--:-- --:--:-- 0 > curl: (60) server certificate verification failed. CAfile: > /etc/ssl/certs/ca-certificates.crt CRLfile: none > It looks like the SSL certificate chain for scan.coverity.com became incomplete sometime between the last successful build (2019-04-10) and today. Browsers that will automatically download missing certs will continue to function, but tools like curl which rely on receiving the full chain will fail. I've sent an email to Coverity to let them know of the issue (if they don't already) and hopefully correct things. - Mike
