Failing analysis ID: bfb329d4-816e-4389-953b-756c2c352d13

SonarQube Cloud
1

Hi,

Yet another error with onboarding. Any advice would be gratefully received, thank you.

Analysis status

The last analysis has failed. If it keeps on failing after several attempts, please contact us on Community forum (opens in new tab) and provide the following failing analysis ID: bfb329d4-816e-4389-953b-756c2c352d13.

2

Hi Michael,

Welcome to the Community! Thanks for the analysis ID, I was able to track it down.

The Autoscan analysis failed on 2026-06-29 14:02:24 UTC because the Sonar TypeScript/JavaScript analyzer encountered a tsconfig.json file inside what looks like a vendored third-party library in your repo (a jqwidgets demo bundle). That tsconfig.json’s include paths don’t
resolve to any files in the checkout, which causes TypeScript to fail with "No inputs were found in config file," and that error aborts the whole analysis.

Failed to parse tsconfig /tmp/.../lsmweb/staff/biosci/modulechange/admin/Content/jqwidgets-ver9.1.4/demos/Angular/temp/tsconfig.json:
  Error: No inputs were found in config file '...tsconfig.json'.
  Specified 'include' paths were '["src/**/*","node_modules/jqwidgets-scripts/jqwidgets-ts"]'

Since Autoscan doesn’t support custom scanner configuration beyond a .sonarcloud.properties file at your repo root, add an exclusion for that vendored bundle so our analyzer skips it entirely. See: Additional analysis configuration

For example:

sonar.exclusions=**/jqwidgets-ver9.14/**/*

(Adjust the path to match wherever that bundle lives in your repo.) This tells the scanner to ignore those demo files, which should let the rest of your project analyze normally.

If you’re not sure which path to exclude, share your repo structure (or the path) here and we can help pin it down. And if you run into this kind of thing again, switching to CI-based analysis gives you more control over scanner configuration than Autoscan does.

Let us know if that helps!

Cheers,

Stevan

3

Hi Stevan,

Thank you very much for your reply. I have switched to the CLI method and this is working perfectly for Framework 4.7.2.

Hopefully this might help someone else with a similar issue

(MSbuild and dotnet methods didn’t work).

- task: SonarCloudPrepare@4
  displayName: 'Prepare SonarCloud Analysis'
  inputs:
    SonarQube: 'YOUR-SonarQube-Connector-here'
    organization: 'YOUR-organization'
    scannerMode: 'CLI'
    configMode: 'manual'
    projectKey: 'Your-SonarQube-projectKey'
    projectName: 'Your-projectName'
    cliProjectKey: 'Your-SonarQube-projectKey' # same as projectKey
    cliProjectName: 'Your-projectName' # same as projectName
    cliProjectSources: '.' # Triggers search relative to the BaseDir defined below
    extraProperties: |
      sonar.projectBaseDir=$(Build.SourcesDirectory)/your/source/directory
      sonar.exclusions=**/Bin/**, **/bin/**, **/obj/**, **/*.dll, **/*.png, **/*.jpg, **/*.gif, **/*.psd, **/*.pdf, **/*.gz, **/PrecompiledWeb/**, **/staticfiles/**, **/Content/fontawesome*/**
      sonar.c.file.suffixes=-
      sonar.cpp.file.suffixes=-
      sonar.objc.file.suffixes=-
      sonar.cs.vscoveragexml.reportsPaths=$(Agent.TempDirectory)/**/*.coveragexml

Best wishes,

Mike