Describe the bug
When integrating with GitLab, a new stage named "external" with a job named "SonarQube" is created. By clicking this job, the user is taken to sonarqube page.
To Reproduce
Steps to reproduce the behavior:
Create a gitlab-ci pipeline with a job to trigger a scan in sonar
Set the project ID in gitlab
Run the scan in a merge request
Look at the pipeline jobs -- a new job "SonarQube" in stage "external" is created.
This is working as per expectations. Sonarqube is decorating your MR with findings, so Gitlab reports this as a job. Since it isn't the output of a step in Gitlab CI it gets reported as an 'External' step.
Describe the bug When integrating with GitLab, a new stage named "external" with a job named "SonarQube" is created. By clicking this job, the user is taken to sonarqube page.
To Reproduce Steps to reproduce the behavior:
Expected behavior No jobs are added
Screenshots
Software Versions
Additional context nothing to add