"The file was removed, no source code can be displayed."

SonarQube Cloud
1

Hello,

I submitted C++ code to SonarQube Cloud.

  • ALM: Gitlab
  • CI: Jenkins
  • Scanner command:
Running SonarScanner with following arguments: -D'sonar.organization=xxxxx' -D'sonar.sourceEncoding=UTF-8' -D'sonar.cfamily.compile-commands=../../../bin/sonar-build-wrapper/compile_commands.json' -D'sonar.projectBaseDir=yyyyy' -D'sonar.pullrequest.key=252' -D'sonar.pullrequest.branch=Qt_lupdate' -D'sonar.pullrequest.base=develop'

*Language: C++

The Sonar analysis reports some issues, and when I want to get info about them, I get in the web GUI:

The file was removed, no source code can be displayed.

I do have the rights on the files, as all members of the organization (and i am one of the administrators)

2

That sounds frustrating. It may be a branch or commit mismatch—check that SonarQube is analyzing the same source revision as GitLab.

3

Hi @Oodini,

This message has two possible causes:

1. “See Source Code” permission: This is the most common cause. Even as an org administrator, if the “See Source Code” permission isn’t explicitly granted at the project level, SonarQube shows this message instead. Check under Project → Administration → Permissions and confirm that your user or group has “See Source Code” enabled.

2. File path resolution in PR analysis: Since you’re running a PR analysis with sonar.projectBaseDir and a compile_commands.json, the file paths SonarQube indexed may not be matching what it’s trying to display. A few things to verify:

  • Are you viewing the issue within the correct PR context (PR #252 / branch Qt_lupdate)? Switching to a different branch or the main branch view can trigger this message if that file wasn’t analyzed in that context.
  • Do the file paths in your compile_commands.json resolve correctly relative to the sonar.projectBaseDir you’ve set? A mismatch here can result in issues being reported but files not being viewable.

Could you confirm whether the permission check resolves it, and if not, share what the exact path looks like in the scanner logs for one of the affected files?

Best regards,

Stevan