I’m having trouble getting SonarCloud to work with our branch folder. We’re using Azure DevOps and one of the branches we use contain releases. These are setup as follows:
Whenever I try to analyze a pull request I get the following error:
ERROR: Error during SonarQube Scanner execution
ERROR: Pull request with branch does not exist on server: releases/1.0
I’ve tried fiddling with sonar.branch.name but haven’t got that to work. Any help is appreciated.
Is your target branch scanned on SonarCloud prior to using it as a target for your pull request?
Hi Colin, thank you for your help.
My releases branches are not being scanned by SonarCloud prior to use. I added them to my long living branch policies and kinda expected them to just work when first being run.
We’re now looking into scanning these said releases branches when they are being initialised, expecting things to work
This causes confusion from time to time amongst our engineers. It would be great if the error message was a bit more instructive, e.g.
Target branch <target_branch> must be scanned by SonarQube before pull request branch analysis can be performed