I’m working on an application that was written primarily in ASP.NET WebForms, but has portions of the application now written in Angular. The application is built using Azure DevOps pipelines, and the ASP.NET portion and Angular portions are built in parallel using jobs, each with their own tests running on that job.
What are my best options for analysing the application in SonarQube? If I want to have just a single multi-language project in SonarQube, can I have both jobs doing their own SonarQube analysis and publishing the results to SonarQube? Or do I have to give up on parallelisation and have the ASP.NET and Angular steps all run as part of one Azure job?
Hi @milbrandt and thanks for your response. Not the best of news, of course, but it’s good to have a definitive answer one way or another.
In the end, I settled for SonarQube monitoring the ASP.NET build, and it still ran its analysis over the TypeScript code, so I’m getting partial coverage of the Angular portion of my app, I guess the only thing missing is that I’m not getting code coverage reports from Angular aggregated into my SonarQube project, but at least I can still publish those reports within Azure DevOps, so the information is available somewhere.
This app has been around for about 20 years, so it’s not surprising that when SonarQube gets run over it for the first time, we see 18K issues identified, and JavaScript is claiming the lion’s share
