Hi @bcipollone,
Thanks for your response.
However, may I suggest you and the SonarQube team please kindly update your documentation on Azure DevOps integration (or a general place for integration rules which apply to ALL SCM and CI tools) to have the flag mentioned and explained, please?
As you might be aware, if you and we do not want to use Bitbucket Cloud (and hence its pipelines), NORMALLY we do NOT read any documentation related to Bitbucket Cloud. If a general rule applies to Azure DevOps and ALL other SCM and CI tools, how much effort would it take for you to document it in 1 central place as the general rule for all SonarQube users to gain the correct understanding?
- that would have saved us/me lots of our time googling around and apparently finding (wrong) workarounds
- interestingly, as you might have read the response from the SonarQube Support team on Azure DevOps at Azure DevOps: how to break CI build if quality gate conditions fail to meet - #4 by Daniel_Meppiel, this is totally opposite to what you have taught me so far
- that response from our reliable source actually made me believe that I MUST SEEK ALTERNATIVES while indeed SonarQube has already implemented the correct solution. That was why I did not create this support ticket in the first place and wasted 2 days of my trial (and hundreds of build minutes on Azure) on finding something useless and unnecessary.
This is not a complain, please do not get me wrong. I simply wish that no one else would have gained the wrong impression and understanding as I did (and apparently wasting their time chasing their own tail).
Your kind help, effort, and tutoring so far is greatly appreciated, Brian.
Thank you.
Nick P