We are migrating our application to monorepo for the last few years. We are using AzureDevOps as CI/CD with source code located on GitHub. More than 100 SonarCloud projects belong to monorepo. Sometimes we have wrong results for Sonar checks inside PR, if there are few pipelines builds, PR will have results from the latest one. So if the first failed and the second is ok - PR will be ok, and that is wrong.
So we are researching monorepo approach on SonarCloud to fix that. But after reading the documentation and doing some tests, it turns out that it is not possible to activate monorepo support for an already existing project with code located on GitHub. Monorepo could be used for newly created projects or activated for existing projects if source code is located on AzureDevOps.
Based on our findings, I do have few questions:
- Is this possible to migrate existing projects to monorepo support without recreating them in any way? Workarounds? By requests? We could not remove and create SonarCloud projects for each pipeline.
- Will SonarCloud project with source code located on GitHub have a feature for adding an existing project to monorepo as it has for source code inside AzureDevOps?