I already have a sonar project configured and being analyzed tied to a Github repo which is not setup as a mono-repo in sonar bindings. But, now I want to create new sonar projects for different directories in same repo but I couldn’t bind new projects to earlier github repo as it wasn’t setup as a mono repo in Sonar. Is there way to change repository binding to mono-repo for existing sonar project?
Context: I have code for 4 different languages - dart, js, kotlin and swift and I think it would be ideal to have separate coverage reports by having different sonar projects to analyze.
ALM used - GitHub actions
CI system used - GitHub
Scanner command used when applicable (private details masked)
I think your best bet here is to delete the existing project and start over. While it’s possible to change the binding of a project, my experiments don’t make it look like you can change the type of the binding (i.e. from repo to mono repo.)
Would you mind sharing why? As you’re hopefully aware, you can natively analyze all those languages as part of a single project. Why do you want to separate the coverage reports?
Hi Ann - thanks for responding. The different projects in repo which are in different languages are kinda independent and I feel having separate coverage reports would be cleaner to say if coverage fails then we exactly know which project is causing it. Without that, we need to drill down from a single report to find directories/files that caused the problem. But, I don’t mind deleting existing sonar project and create again with a mono-repo. Just wanted to double-check that I am not missing anything.