# Combining Azure DevOps jobs into single SonarQube project **URL:** \ **Category:** SonarQube Server / Community Build\ **Created:** [April 15, 2025, 6:55am UTC](https://community.sonarsource.com/t/combining-azure-devops-jobs-into-single-sonarqube-project/138801 "2025-04-15T06:55:11Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![davidkeaveny](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/davidkeaveny/32/45163_2.png) [@davidkeaveny](https://community.sonarsource.com/u/davidkeaveny)\ **Post date:** [April 15, 2025, 6:55am UTC](https://community.sonarsource.com/t/combining-azure-devops-jobs-into-single-sonarqube-project/138801/1 "2025-04-15T06:55:11Z")
I’m working on an application that was written primarily in [ASP.NET](http://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](http://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](http://ASP.NET) and Angular steps all run as part of one Azure job? ---
**Author:** ![milbrandt](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/milbrandt/32/3726_2.png) [@milbrandt](https://community.sonarsource.com/u/milbrandt)\ **Post date:** [April 15, 2025, 7:22am UTC](https://community.sonarsource.com/t/combining-azure-devops-jobs-into-single-sonarqube-project/138801/2 "2025-04-15T07:22:39Z")
Hi @davidkeaveny You are not allone - but unfortunately, SonarQube analysis only really works with a single job. See also the other threads here in the forum,e.g. - [Azure Devops Pipeline multiple jobs](https://community.sonarsource.com/t/azure-devops-pipeline-multiple-jobs/135968/1) - [Provide test results from multiple steps](https://community.sonarsource.com/t/provide-test-results-from-multiple-steps/26365/1) ---
**Author:** ![davidkeaveny](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/davidkeaveny/32/45163_2.png) [@davidkeaveny](https://community.sonarsource.com/u/davidkeaveny)\ **Post date:** [April 15, 2025, 10:29pm UTC](https://community.sonarsource.com/t/combining-azure-devops-jobs-into-single-sonarqube-project/138801/3 "2025-04-15T22:29:17Z")
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](http://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 😀 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/d/7/d75dfafd13d43c11a87c6545164c7028016de61c.png) ---
**Author:** ![system](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/system/32/31083_2.png) [@system](https://community.sonarsource.com/u/system)\ **Post date:** [April 22, 2025, 10:29pm UTC](https://community.sonarsource.com/t/combining-azure-devops-jobs-into-single-sonarqube-project/138801/4 "2025-04-22T22:29:43Z")
Closed on April 22, 2025, 10:29pm UTC This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.