We have had several occurences where the analysis is triggered, runs well and is green, and even adds a comment to the Pull Request, but the CI check does not pass.
I would think of a misconfiguration of my part, but the PR comment makes me think that Sonarcloud has all the access it needs
Any idea on what I could try? For now, the workaround is for devs to ask a user with Github admin privileges to bypass the checks, as the SonarCloud PR comment is readily available, it’s not too much hassle, but still.
This seems to be affecting us also, we’re using the Sonar Scanner CLI in Azure DevOps and the bot will post a message but isn’t setting the check anymore on the PR.
Is there a way we can identify whether we’re having the same issue? Something to look for in the logs? I’ve just tried setting up PR decorations with checks. While everything seems to be working fine, and we’re receiving comments in the PR, there is no check appearing.
Also, when the fix is done, I hope there will be adequate tests to try to avoid such regression in the future. That’s the kind of thing we use sonar to verify on our applications.
This issue seems to have resurfaced. This time it’s sporadic though. Both the analysis summary and check status is updated correctly at times. But for other PRs, neither comes through although the analysis itself completes and can be observed on sonarcloud.io.
Sometimes just re-running the analysis does the trick.
Thanks for notifying us of this bug. We have identified the cause and are working on the fix.
You can follow the resolution here. We will also update this thread once the issue has been fixed.