Shortly after the fix for this issue “Azure DevOps + Unbound repos PR decoration incident”, the issue with Azure DevOPS quality gate came back (only worked for about a day or so). The results of the Sonarcloud analysis are sent to Sonarcloud correctly, but Sonarcloud isn’t able to update the quality gate on Azure DevOPS. The information of our configuration are below.
We were able to diagnose on our side that when we try to create a new status on the PR we receive a 401 Unauthorized response from Azure DevOps. My suspicion was that the access rights at the PAT were not fully configured. All GET calls to Azure DevOps were successful, only the POST call to create a status was unauthorized. I asked @Francis to double-check whether the configured had the appropriate write rights.
The token did have the correct rights on their side, and was displayed as valid on SonarCloud.
@Francis ended up generating a fully new PAT and storing this PAT on both the Organization settings, and for each project under General Settings > Pull Requests. This ended up resolving the issue. Could you check if the same approach would work for you @Lootvoet?
