Getting Gitlab MR decorator to work on self-hosted instance

Hello,

I am trying to get Gitlab MR decorator working.

Here is the versions used.

  • SonarQube (self-hosted ; installed via official :whale: Docker image) version 8.2 (build 32929), Developer Edition
  • SonarQube Scanner 4.2.0.1873
  • Gitlab (self-hosted) version 12.8.1 (d18b43a5f5a), Community Edition

I have configured the Gitlab tab of the ALM Integrations settings pane with my custom Gitlab instance API URL and token and it shows that Merge Request Decoration is enabled.

The analysis is triggered properly and the Merge Request appear on SonarQube Server on the dropdown list used to switch the branch/MR but, when I select my Merge Request, SonarQube Server warns that Last analysis had 1 warning.

When I click on 1 warning, it shows a modal dialog saying that Pull request decoration did not happen. Unable to find a Pull Request decorator for provider ‘GitlabServer’.

Am I forgetting something in the configuration here of is this just a bug ?

Thanks for your help :smiling_face_with_three_hearts:

Hey there!

Are you setting sonar.pullrequest.provider in your analysis configuration anywhere? I ask because if you are – you should remove it, and make sure you’ve assigned the correct provider in your Project Settings > General Settings > Pull Request Decoration

Hello @Colin :wave:

Thanks for your reply :slight_smile:

I do not set sonar.pullrequest.provider in my analysis configuration and the Pull Request Decoration configuration for the project is also defined.

pr-deco

Hey :slight_smile:

Hm, it has to be coming from somewhere, because SonarQube doesn’t even understand GitlabServer as an option for sonar.pullrequest.provider.

Is there a particular CI tool that you’re using to trigger/execute the analysis?

Colin

1 Like

Thanks for pointing me to the right direction.

I have dumped the database to be able to conduct a full text search on GitlabServer and found out old properties in the properties table related to a plugin that I had tested before buying Developer edition and that were conflicting.

I just deleted the conflicting properties of the old plugin from database manually and it now works perfectly :ok_hand:

Thanks again for your help :+1:

Is there a feature request to add GitLab as a pull request provider ? Our organization would like to get it added to sonarcloud.