It looks like here you’re failing the build with the sonar.qualitygate.wait=true analysis parameter.
You can apply that to your other project, but it still begs the question: why do you have an Azure DevOps bound organization if all your projects are not in Azure DevOps?
Ok many thanks for the insight, been too bothered/overwhelmed by the issues I am facing to remember that option might be missing in the .Net configurations
As for the binding to Azure DevOps. … that was done by mistake and now it’s becoming a regret. … if you guys can assist in removing it from the backend . …it would be great though
I will try that sonar.qualitygate.wait=true flag and re run the flow and see the outcome
It’s not possible. But you can always create a new org, bound to the appropriate DevOps platform.
If you have a yearly subscription for your current organization, a new coupon can be issued for your new organization by reaching out to your sale representative.
If you have a monthly subscription by credit card, you can simply stop your subscription on the old organization and re-subscribe on the new one.
Hi @Colin
You are such a life saver. … what can I do without you?
My Quality Gate are now on flick.
And Yes, while I will not want to stop the monthly subscription halfway I will wait till we have a day or 2 left in the cycle and then initiate the new organization
In the meantime, the Quality Gates are working and I may not need to do that any more