We use SonarQube analysis in our Azure Devops build pipelines. For some users, when they create the SonarQube Endpoint, the build pipeline works perfectly. For others, when they create it, with the same url and token, the SonarQube prepare step fails with a 403 Forbidden error. I tried with the local SonarQube scanner and used the same token and url successfully. The only difference between successful and unsuccessful builds is the user who created the Service Connection in Azure Devops.

What can we do to solve this strange situation?

0 Answers