-
-
Notifications
You must be signed in to change notification settings - Fork 530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure Devops: mono repo support #361
Comments
No, the analysis name would currently clash between different runs in Azure so overwrite the existing pipeline. The existing change should be easy to extend to cover all decorators though. |
Thank you for your response! If the project name is added like in the Github solution, this would potentially break existing DevOps builds, as the name of the StatusCheck in DevOps is modified. |
Yes, if the project is configured to depend on a status check with a particular name then renaming the Status Check will cause problems, however without having checks named differently then there's no way to support monorepos. I've implemented my proposed approach in #391, could you take a look and provide any feedback please? |
Hi thank you for your work it is highly appreciated! |
Released in 1.9.0 and 1.8.1 |
Hi,
are mono repos supported with this plugin?
We have .NET and Angular projects mixed in a single repository. If we create a PR are the comments and the quality gate then merged when consecutive sonar analysis are executed in separate pipelines?
I see a merged PR with the issue #213. But this is only for GitHub,
Thank you!
The text was updated successfully, but these errors were encountered: