"Bind project" to GitLab doesn’t work on SonarQube Community

SonarQube Server / Community Build
,
1

Versions

  • SonarQube Community Build: sonarqube:25.10.0.114319-community, reproduced on sonarqube:25.11.0.114957-community as well

  • Scanner / Plugins / Extensions: not involved in this reproducer (UI/API only), no 3rd-party plugins installed.

Deployment

Docker (official images listed above)

What I’m trying to achieve

Bind an existing, already-created local project in SonarQube to a GitLab repository, after having configured the global GitLab DevOps Platform Integration.

What I’ve tried so far

The GitLab integration under “Administration” > “DevOps Platform Integrations” works fine. I can create new projects directly from GitLab without any problem, the onboarding flow completes successfully and the new project shows up properly bound to the GitLab repo.

However, if I try to bind an already existing project (using the “Bind project” link next to its name), I immediately get the error:
Unknown url : /api/alm_settings/set_gitlab_binding

Checking the Web API docs, it seems this endpoint does exist in the Community Build, it’s only present in commercial editions. If project creation from GitLab works (and it clearly does), it feels inconsistent that binding an existing project doesn’t.

2

Thanks for the report! We already have this ticket (SONAR-25899).

3

(post deleted by author)