Run Merge Requests via secondary/different runner

Hi all,
I’m using SQ v8.6.0.39681

  • what are you trying to achieve
    We have our sonarQube instance configured to analyze merge requests and our master branch.
    The issue is sonarQube uses the same runner agent to analyze merge requests and master branch. This is causing issues/blocking us during deployment window as the runner is often busy analyzing merge requests, when it should be analyzing master branch. Is there anyway we can have sonarQube use a different runner for merge requests?
  • what have you tried so far to achieve this
    I went through documentation and online search.

Any help is greatly appreciated.
Thank you

Hi,

To be clear, are we talking about the CI-side runner or the backend analysis report processing?

 
Ann

Hi, the CI-runner side.

The gitlab runner, I can create multiples but I’m not sure how to configure SQ to use one for merge requests and another for master commits.

Thank you

Hi,

This isn’t about configuring SonarQube, it’s about configuring GitLab. And sorry, but I don’t have any experience there. You might try in the GitLab forum if such a thing exists.

 
:woman_shrugging:
Ann

Thank you for the guidance.