Error observed
I’m currently migrating from SonarQube to SonarCloud and since I’m also migrating the SonarQube-Plugins to Gradle-Plugins, I have a lot of new warnings in files, I didn’t change. When I look in my feature-branch, everything looks great, but when I execute the exact same project to report to the master-branch, I then see the new warnings which are not related to the source-files I changed.
Steps to reproduce
add gradle-Checkstyle-Plugin in short-lived branch
execute gradle sonar for short-lived branch → no new warnings
execute gradle sonar for main-branch → many new warnings
While SonarQube has collapsed short and long-lived branch into the same concept (just a branch), SonarCloud still works with short/long-lived branches where the former only raise issues on old code.
ok, I saw that option, but it’s unclear to me, whether “new code” on long-lived branch is every single commit or all commits on that branch?
For main-branch I would prefer “every commit” as “new code”, but on all other “all commits on this branch” to have similar behavior to SonarQube.
And one more general question: I thought that SonarQube and SonarCloud only differ on hosting and 3rd party plugins, but now there’s also the short/long-lived branch handling. Are there any more differences?
They are different products, which have at time diverged from each other offering the same analysis engine, but some different features / implementations. I don’t have a comprehensive list of differences to share.
For end-user (developers) experience it’s still strange. Developers just want a SaaS to replace the self-hosted SonarQube and what they get is something else with only very limited information… I hope that both products will soon have almost equal features/implementations.
I agree with you. We hope to see more alignment in our products soon as we focus more on the Sonar solution, rather than individual products. This will take some time.
