Sonar cloud scanning on the development branch and input options

SonarQube Cloud
,
1

I am scanning through the development branch, getting the following
INFO: Sensor PL/SQL Sensor [plsql]
WARN: The Data Dictionary is not configured for PLSQL analyzer which prevents rule(s) S3641, S3921, S3618, S3651 to raise issues. See https://sonarcloud.io/documentation/analysis/languages/plsql/
INFO: 1 source files to be analyzed
WARN: Invalid character encountered in file <path>/public/assets/file.sql at line 86 for encoding UTF-8. Please fix file content or configure the encoding to be used using property 'sonar.sourceEncoding'.

I’ve added the following in my bitbucket pipeline:

Blockquote
inputs:
extraProperties:
sonar.tsql.file.suffixes = sql,tsql
sonar.plsql.file.suffixes = pks,pkb

under my steps

but I still get it stuck:
INFO: 0/1 files analyzed so far, currently analyzing: <path>/public/assets/file.sql
INFO: 0/1 files analyzed so far, currently analyzing: <path>/public/assets/file.sql
INFO: 0/1 files analyzed so far, currently analyzing: <path>/public/assets/file.sql
INFO: 0/1 files analyzed so far, currently analyzing: <path>/public/assets/file.sql
INFO: 0/1 files analyzed so far, currently analyzing: <path>/public/assets/file.sql
INFO: 0/1 files analyzed so far, currently analyzing: <path>/public/assets/file.sql
INFO: 0/1 files analyzed so far, currently analyzing: <path>/public/assets/file.sql
INFO: 0/1 files analyzed so far, currently analyzing: <path>/public/assets/file.sql

and the pipe failes

2

Fixed it… confs are on the cloud saas interface, not via conf or pipe files

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.