Greetings,
Our company is using SonarCloud integrated with Gitlab CI/CD for a Node JS based project.
We configured the following stage in .gitlab-ci.ymlaccording to documentation:
quality-test-job:
stage: quality-test
image:
name: sonarsource/sonar-scanner-cli:latest
entrypoint: [""]
cache:
key: "${CI_JOB_NAME}"
paths:
- .sonar/cache
script:
- sonar-scanner
-Dsonar.projectKey=$OUR_COMPANY_$OUR_PROJECT
-Dsonar.organization=$OUR_COMPANY
-Dsonar.qualitygate.wait=true
-Dsonar.qualitygate.timeout=300
only:
- master
- stage
- merge_requests
During commits at master and stage branches as well as during any merge requests we correctly receive an analysis in our SonarCloud platform.
Problem is, regardless of configuring sonar.qualitygate.wait and sonar.qualitygate.timeout the job is not waiting for Quality Gate response in order to stop the pipeline if the code does meet gate requirements.
From our understanding this feature should already be live according to:
https://jira.sonarsource.com/browse/MMF-1791
Does anybody have insights on this matter?
Thanks