clone:
depth: full # SonarCloud scanner needs the full history to assign issues properly
addons:
sonarcloud:
organization: “sonarcloud”
token:
secure: “j21c797ea979954bd4a5fd66f8bf6209fb476e18e”
In the given sample code, only a sonar scan is available.
Sonar quality gate is not configured (sonarcloud-quality-gate) in that example. Do we need to add any code for sonar quality gate ? Or the above code covers both sonar scan and sonar quality gate ?
You can add /d:sonar.qualitygate.wait=true as an analysis parameter to fail the pipeline if your Quality Gate fails. You cannot use the sonarcloud-quality-gate pipe in this context.
You’re probably safe adding the quotation marks to match the rest of your parameters – but don’t take my word for it. The best thing you can do is… try it!