The behaviour should be the same as former alerts - except that it will be simpler as only 1 quality gate will be linked to the current project (whereas several alerts coming from several quality profiles could be executed in 4.2 with multi-language):
- at the end of a project analysis, find the associated QG
- if there's one, execute the conditions and generate the same information as before:
- Quality Gate Status
- Quality Gate message
- the Quality Gate Status metric is the metric with "alert_status" key, renamed from an end user point of view
Once this is done, this means that we can verify that the quality gate concept works and provides the correct information.
Note: the property to set a quality gate on the CLI is "sonar.qualitygate".