SonarQube Cloud Analyze step in DevOps pipeline - JavaScript/Typescript analysis timing out

SonarQube Cloud
, ,
1

We are experiencing a timeout issue on one of our projects using the SonarQube Cloud Analyze step. No changes have been made recently to our pipeline or any code surrounding the pipeline. The analysis seems to stop at the JavaScript/Typescript analysis step.

Relevant line in azure-pipelines.yml:

- task: SonarCloudAnalyze@3
  inputs:
    jdkversion: 'JAVA_HOME_17_X64'

Relevant logs (check the timestamp near the bottom, the build cancels itself out after 60 minutes):

2026-03-02T14:24:26.9561704Z INFO: Sensor JavaScript/TypeScript analysis [javascript]
2026-03-02T14:24:27.5523057Z INFO: Detected os: Windows Server 2025 arch: amd64 alpine: false. Platform: WIN_X64
2026-03-02T14:24:27.5529483Z INFO: Deploy location C:\Users\VssAdministrator\.sonar\js\node-runtime, tagetRuntime: C:\Users\VssAdministrator\.sonar\js\node-runtime\node.exe,  version: C:\Users\VssAdministrator\.sonar\js\node-runtime\version.txt
2026-03-02T14:24:30.2442478Z INFO: Using embedded Node.js runtime.
2026-03-02T14:24:30.2444187Z INFO: Using Node.js executable: 'C:\Users\VssAdministrator\.sonar\js\node-runtime\node.exe'.
2026-03-02T14:24:32.8493916Z INFO: Memory configuration: OS (8186 MB), Node.js (2240 MB).
2026-03-02T14:24:33.0227464Z INFO: WebSocket client connected on /ws
2026-03-02T14:24:33.0230003Z INFO: Plugin version: [12.0.0.38664]
2026-03-02T14:24:36.1146875Z INFO: Some of the project files were automatically excluded because they looked like generated code. Enable debug logging to see which files were excluded. You can disable bundle detection by setting sonar.javascript.detectBundles=false
2026-03-02T14:24:36.4280765Z INFO: Found 2 tsconfig.json file(s): [D:/a/1/s/{{ProjectName}}/ClientApp/tsconfig.json, D:/a/1/s/{{ProjectName}}/bin/Release/net8.0/ClientApp/tsconfig.json]
2026-03-02T15:15:30.8098802Z ##[error]The Operation will be canceled. The next steps may not contain expected logs.
2026-03-02T15:15:31.1151471Z ##[error]The operation was canceled.
2026-03-02T15:15:31.1158528Z ##[section]Finishing: SonarCloudAnalyze

I suspect that there may be some code that is being analyzed twice. I noticed that our /bin/ folder is being included, though it seems like we have set it to be excluded.

2026-03-02T14:24:14.1846790Z INFO: Indexing files of module '{{ProjectName}}'
2026-03-02T14:24:14.1853449Z INFO:   Base dir: D:\a\1\s\MarketingSchools\mySchool
2026-03-02T14:24:14.4318895Z INFO:   Source paths: appsettings.json, appsettings.PROD.json, appsettings.QA.json,...
2026-03-02T14:24:14.4324640Z INFO:   Included sources: {{ProjectName}}/**
2026-03-02T14:24:14.4327397Z INFO:   Excluded sources: **/bin/**, **/obj/**, **/wwwroot/**, **/node_modules/**, **/bin/Release/net8.0/ClientApp/src/app/**, **/angular/cache/19.2.0/babel-webpack/**, **/build-wrapper-dump.json
2026-03-02T14:24:14.4328308Z INFO:   Excluded sources for coverage: *
2026-03-02T14:24:14.4401828Z WARN: Specifying module-relative paths at project level in the property 'sonar.coverage.exclusions' is deprecated. To continue matching files like '{{ProjectName}}/appsettings.json', update this property so that patterns refer to project-relative paths.
2026-03-02T14:24:14.6872952Z INFO: Indexing files of module '{{ProjectName}}'
2026-03-02T14:24:14.6873880Z INFO:   Base dir: D:\a\1\s
2026-03-02T14:24:14.6875040Z INFO:   Source paths: {{AnotherProjectName}}/azure-pipelines.yml, MarketingSchools/azure...
2026-03-02T14:24:14.6876225Z INFO:   Test paths: {{ProjectName}}/bin/Release/net8.0/ClientApp/src/app/...
2026-03-02T14:24:14.6886866Z INFO:   Included sources: {{ProjectName}}/**
2026-03-02T14:24:14.6887642Z INFO:   Excluded sources: **/bin/**, **/obj/**, **/wwwroot/**, **/node_modules/**, **/bin/Release/net8.0/ClientApp/src/app/**, **/angular/cache/19.2.0/babel-webpack/**, **/build-wrapper-dump.json
2026-03-02T14:24:14.6888345Z INFO:   Excluded sources for coverage: *
2026-03-02T14:24:14.6904095Z INFO: 1272 files indexed (done) | time=693ms

Any suggestions on how to fix this time out issue? It is currently only affecting 1 of our several projects that use the SonarQube Cloud for analysis and it seems that nothing has changed on our end that would have affected this process. We started experiencing issues earlier this week.

2

Hi,

Can you add sonar.debug=true to your analysis command line and provide the resulting log in full, starting from the analysis command itself and redacted as necessary?

 
Thx,
Ann

3

sonarcloudanalysis.log (1.1 MB) We have tried excluding the files that the process is hanging on, but it just hangs on a different file.

5

Hi,

Thanks for the log.

What can you tell me about Repo2/mySchool/ClientApp/src/app/models/freshAddressResponse.ts? Is it particularly long? Complex?

 
Thx,
Ann

6

It is not. I’ve added it below. When we first saw the issue, it hung on a particular file that is very long, so I excluded that one, but then it hung on a different file that was not as long or complicated. I excluded that one and now we are stuck on this simple model. I should note that this worked as recently as 3/2 and started failing on 3/4.

export class FreshAddressResponse {

  invalid: boolean;

  finding: string;

  comment: string;

  commentCode: string;

  submittedEmail: string;

  suggestedEmail: string;

  suggestedComment: string;

  errorResponse: string;

  uuid: string;

  apiError: boolean;

}
8

Hi,

No, that is certainly not long or complex. :thinking:

I’ve flagged this for the team.

 
Ann

9

Hello @knyland and @Shelly_Noll ,

just to pinpoint where the issue may be, can you add this property to your analysis?

sonar.jasmin.internal.js.ts.disabled=true

Please, let me know if the analysis still fails after adding that property

Cheers,
Victor

11

It is still getting stuck around 6600~ lines into the analysis.

12

Hi @Shelly_Noll,

can you share again the full debug logs with that property set? Also, just to discard a memory issue, can you try increasing nodejs memory to sonar.javascript.node.maxspace=16384?

Cheers

13

I set the maxspace and got the same results.

sonarcloudanalysis_20260310.log (1.1 MB)

1 Like
14

From the private messages with @Shelly_Noll:

  • JS/TS analyzer has a bug on rule S2077. The fix will be released in the upcoming SQ version.
  • The user was able to unblock the analysis by disabling that rule or changing the code triggering an infinite loop. var min = min; to var min;

Cheers,
Victor

1 Like