Jakub Vavrik

Exactly the same happens to me with v1.7.0.

> @javamachr could you open your fork to accept issues? I just enabled it - wasn't aware its disabled 🤦🏻‍♂️

I believe it is not currently possible - see https://sonarsource.atlassian.net/browse/FR-8 where Sonar does not has this feature on roadmap. Regarding new issues - I believe this kind of depends on...

Seems like config issue - one of projecId or refName is empty. Check $CI_COMMIT_REF_NAME or $CI_PROJECT_PATH value if it is correctly set.

The project ID value is wrong. It is not path it should be ID of project(it is queried by ID via API) that you can find on project page: 

It seems that it fails to find the project via API. This ```bash -Dsonar.gitlab.url=https:/mygitlab.com ``` seems like a wrong value - could you please double check that it is correctly...

It is checking gitlab API using sonar.gitlab.url=https://git/ and projectId and it obviously fails since https://git/ seems to be wrong value and no gitlab server is running there I assume.

Hmm can you try to call the API from sonar machine/container via CURL? It should give you some hints. For some reason sonarqube is unable to reach gitlab api calls....

Hmm then it might be related to JAVA not working with that URL. What certificate do you use on gitlab instance? With self signed you might need to add CA...

Do you mean DB of Sonar or DB of Gitlab? AFAIK it should not have any impact on this as it only reports results to GitLab via API.