Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sonarqube converter - no issue in output file #3324

Open
mnelli19 opened this issue Feb 28, 2025 · 2 comments
Open

Sonarqube converter - no issue in output file #3324

mnelli19 opened this issue Feb 28, 2025 · 2 comments

Comments

@mnelli19
Copy link

Hi,
I'm trying the sonarqube converter with sonarqube enterprise v10.8.1 but no issue is reported in the output file.
I have no error in the execution but (even if I put log level verbose it doesn't write anything during the execution).
It generates the output json file but inside there are no issues, only this part

{
"platform": {
"name": "Heimdall Tools",
"release": "2.11.3",
"target_id": ""
},
"version": "2.11.3",
"statistics": {
"duration": null
},
"profiles": [
{
"name": "Sonarqube Scan",
"version": null,
"title": "SonarQube Scan of Project Branch main",
"maintainer": null,
"summary": "SonarQube Scan of Branch main",
"license": null,
"copyright": null,
"copyright_email": null,
"supports": [],
"attributes": [],
"depends": [],
"groups": [],
"status": "loaded",
"controls": [],
"sha256": ""
}
]
}

This is the command used:
saf convert sonarqube2hdf -L verbose -n -u -a -b main -o sonarqube-scan.json

Any suggestions?

@Jiri-Stary
Copy link

I would try if you are using a token with enough permissions that can pull the issues via the sonarqube api - maybe thats what returning empty list. I would recommend checking what you can pull via the sonarqube api directly.

The command looks ok,
In my project with different version i use somewhat similar

convert sonarqube2hdf -n *** -u *** --auth *** -o ./hdf/sonarqube_scan.json

@mnelli19
Copy link
Author

mnelli19 commented Mar 1, 2025

Thank you @Jiri-Stary but I checked and using the same token I can retrieve the issues via api (/api/issue/search), but with that same token I have the empty json as indicated. I'm also using an administrator account.
Unfortunately, as mentioned, the other strange thing is that by setting the log level to verbose nothing is written and therefore I don't have any other indication.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants