Background tasks getting stuck with GitLab pull request decoration

SonarQube Server / Community Build
,
1

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
    SonarQube: 8.4.2
    Scanner: 4.4.0.2170
    Self Hosted GitLab: 12.10.1

  • what are you trying to achieve
    Setting up pull request decoration with GitLab

  • what have you tried so far to achieve this
    We have followed the SonarQube documentation. Pull request analysis works just fine, but if we use Pull request decoration feature with our GitLab instance, after just 1 or max 2 attempts, the background tasks start to get stuck. Once that happens, only way forward is to remove project from SonarQube and set it up again with a new Name and Key.

We have run multiple tests on different instances, including our Staging and Production instances. But every time we start using Pull request decoration, we have this issue with the background tasks.

We are soon rolling out EE of SonarQube for all our developers and we need to be able to allow our devs to use Pull request analysis with our self-managed GitLab instance. But due to the above mentioned issue, we aren’t able to use this functionality.

I am not sure if it is a bug and then we are using slightly older version of GitLab (12.10). That’s why I have not posted this as a bug. But if required, I will happy to file a bug.

Can someone with knowledge on the subject help us resolve the issue? Appreciate your help in advance!

Best
Saurabh

2

cc: @Fabrice_Bellingard

3

Hey there. Since you just posted your topic, you should not immediately start pinging people who aren’t a part of your thread. :slight_smile: It’s frowned upon in this forum.

As you’re using Gitlab, please see SONAR-13290 , which describes an issue where decorating a Merge Request causes a background task to never complete, and a workaround.

4

Hey Colin! I copied Fabrice since he handled the whole GitLab and SonarQube integration, as far as I was able to follow, a few months back. Apologies if that was not needed.

Thank you for pointing out to the issue and the workaround. However, I find it a little strange that an issue with Major priority has been open for more than 6 months and it has not even been assigned. We ended up wasting so much time trying to figure out if we made any mistakes, running tests on different SonarQube instances.

This should also be frowned upon in this forum. :slight_smile: