We are using SonarCloud on private Github repositories, and are experiencing the following issue with PR integration:
- Our CI pipeline (Jenkins) builds our Maven project, and runs the ‘mvn sonar:sonar’ command initializing the project on SonarCloud, if it has not been setup earlier
- In the case where the project has not been initialized earlier, we never get the SonarCloud comments on the PR with the analysis results.
- If we delete the project from SonarCloud, and then initialize it from the list of Github repos on SonarCloud, then we get the comments on the PR, once the PR
Is this expected behaviour, when the repo is not initialized from SonarCloud.io, or perhaps a bug? It introduces a annoying manual step, that we would be happy to avoid.
I am not sure if this is related to this issue in any way: GitHub lost the sonar Check. It could be coincidence that deleting and re-initializing a repository solves the issue.
If you need more details, I can provide this in a PM.