Failing analysis in SonarCloud with automated scan

SonarQube Cloud
1

Hi there,

Can someone check the following ID: 911fe06c-8226-4227-b80f-0453147239cf of a failed analysis please?

Many thanks,

Patrik

2

Hello @phajnal-odevo,

Welcome to the Community! Thanks for reporting this. I looked into the analysis logs associated with analysis id 911fe06c-8226-4227-b80f-0453147239cf for codwellers_odevo-resident-app-server, and found the cause in the scanner logs.

The analysis is failing early, before any code scanning starts, due to an invalid sonar.sources configuration. The scanner log shows:

ERROR: Invalid value of sonar.sources for codwellers_odevo-resident-app-server
ERROR: The folder set-codwellers-libraries.ps1 does not exist for codwellers_odevo-resident-app-server (base directory = the cloned repo root)

Your project’s sonar.sources setting includes a path pointing to set-codwellers-libraries.ps1, and that file does not exist at that location on the bld/2026.02 branch. Since sonar.sources only accepts literal paths, not wildcard patterns, if that
exact path is missing on a given branch, analysis fails outright for that branch rather than skipping the missing entry.

To fix this, you have a couple of options:

  1. Check your project’s analysis scope configuration, either in SonarQube Cloud under Administration > General Settings > Analysis Scope, or in a .sonarcloud.properties file if you’re using one, and confirm whether set-codwellers-libraries.ps1 is meant to be there.
  2. If that file only exists on your default branch and not on bld/2026.02, either remove it from sonar.sources so the setting works across all branches, or make sure the file is present wherever this branch is analyzed.
  3. Since it’s a PowerShell setup script rather than application source code, it may be worth reconsidering whether it belongs in sonar.sources at all.

For reference on how sonar.sources works and how to configure analysis scope, see Analysis scope in SonarQube Cloud, Introduction | SonarQube Cloud | Sonar Documentation . For Automatic Analysis specifically, note that project-level property files like sonar-project.properties are ignored there, configuration needs to go through the UI or .sonarcloud.properties, details are in Automatic analysis,
Automatic analysis | SonarQube Cloud | Sonar Documentation .

Best regards,

Stevan