[Question][SonarQube] Is Enterprise Edition v2025.1.3 supported

[ajoecker1]

Question

Hi. I was wondering whether SonarQube Enterprise Edition v2025.1.3 is supported ?

I have the problem that I can add the connection in DevLake (SonarQube Server) and using "Test Connection" it tells me that "Test Connection Succesfully".

But when I want to add a data scope, I only see an empty box with no options (see screenshot).

Is there anything known or anything to do for me here ?

Screenshots

Additional context

Add any other context here.

[dosubot]

Hi @ajoecker1! I'm Dosu and I’m helping the incubator-devlake team.

DevLake does not explicitly mention support for SonarQube Enterprise Edition v2025.1.3, but there are no restrictions in the code that would prevent it, and the plugin is actively maintained for recent SonarQube versions. Officially, only SonarQube 8 and 9 are listed as supported, with requests open for version 10 and above support, so compatibility with v2025.1.3 may depend on API compatibility—especially with the /api/projects/search endpoint used to fetch projects for data scope selection (source).

The empty data scope issue after a successful connection is most often caused by insufficient token permissions (the token should be created with a system admin account), endpoint misconfiguration (the URL should end with a / and point to the correct SonarQube API), or network/proxy/firewall issues blocking API calls. Some SonarQube APIs require admin rights to list all projects; using a token without these rights can result in an empty list (source). There is also a suggestion to try the /api/components/search_projects endpoint, which may work without admin rights (source).

To troubleshoot:

1. Ensure your token is generated by a system admin account.
2. Double-check the endpoint URL formatting.
3. If possible, test the /api/projects/search and /api/components/search_projects endpoints directly on your SonarQube instance with your token to confirm they return your projects.
4. Check for any proxy/firewall issues that might block API calls.
5. Review DevLake and SonarQube logs for errors when fetching repositories.

If these steps don't resolve the issue, sharing relevant logs or error messages will help with further diagnosis.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[jbsmith7741]

I'm running into the same issue, no repos show even though the test connection is passing. This issue is caused because the token used to connect to SonarQube is not an admin token. This level of permissions isn't required to pull the required data and I've created #8707 to allow searching repos with a non-admin token.