Hi,
regarding your screenshot, i assume those are Java projects.
Usually Java projects are built with Maven, means you should use the SonarScanner for Maven
But your sonar.projectKey naming is not maven like.
Normally projectKey is groupid:artifactid, see analysis parameters
Also
no need to manually create a Sonarqube project, your Jenkins user should have sufficient rights
to create a Sonarqube project, means the project is created with the first build
i guess your projects should be private by default !?
WRT git server (Geritt in your case) <-> Jenkins interaction.
Your git server has configured a global hook, calling Jenkins for every git push event.
Don’t know how this works with Geritt - we use Azure Devops -but that should be possible.
In Jenkins every job / pipeline that has the git repo URL configured will start automatically,
i recommend to use Jenkins multibranch pipelines.
A pipeline will usually have stages like git checkout, build incl. tests, Sonarqube scan,
check Sonarqube quality gate, publish to Artifactory/Sonatype Nexus, deploy.
Gilbert