@Ilham Because our existing coverage is low, we want to be able to track the progress we are making at monorepo root level, org level and individual module level
TBH I am little surprised that this use case isn’t common as lot of companies are in similar boat when it comes to monorepo and I assumed that hierarchical views would be of great help.
We plan to introduce portfolio-level reporting to SonarCloud which might eventually help in this area.
You’ll find a card here where you can share more about your needs and that you can follow.
Can you please tell us more about your tracking needs at the organization level and how you would use such information?
G Ann Cambell (sorry I’m a new user and can’t tag) We’re currently using SonarCloud and a rush monorepo with Typescript. From what I understand I need to send coverage results individually to Sonar for analysis. Is that right? What I’ve done is use the matrix feature of GitHub Actions to search for sonar-project.properties files and extract sonar.projectKey and the folder location of the file. With rush I can execute commands across the monorepo so I can generate all of the coverage with one command but then I use the matrix to upload each project’s result to Sonar. My only issue is the results card from Sonar doesn’t include the projectKey so its hard to know which project each card belongs to. Is there a way to include the project name or key in the results card?