Closed michelebortolato closed 6 years ago
dude, the log says:
Unable found project for my.project.path Verify Configuration sonar.gitlab.project_id
it seems that my.project.path is not a project id, if you're using static definition for testing, you must use the id, this is an integer or the path that you use for clone the repo.
regards.
The name is correct because:
Thanks
if the project is private you need the gitlab user access token, in my testing I use:
-Dsonar.gitlab.project_id=git@git.company.com:Dashboard/myproject.git
using sshUrl as you say works only if i omit the property sonar.gitlab.commit_sha, the error is always the same and seems related to the sha that i pass, i retrieve this from gitlab copying it, it is absolutely right.
This is a problem that affect all the project of my area, 2 weeks ago everything was fine
It was a permission misconfiguration in gitlab, that token could not see any project.
Thanks for the support
hi i'm using "org.sonarsource.scanner.maven:sonar-maven-plugin:3.4.0.905" with this command:
mvn -X sonar:sonar -B -Dsonar.analysis.mode=preview -Dsonar.gitlab.commit_sha=8f6b4946858696f7a7ba928c30d2d6b50daebcc3 -Dsonar.gitlab.project_id=my.project.path -Dsonar.gitlab.ref_name=develop
and the build doesn't work, for this problem:
it works if is omitted "my.project.path" or if i use the numerical id of the project as sonar.gitlab.project_id property, it seems strange for me because i tried every kind of project path, i also get the json gitlab of my project and i am sure that i put the right name, i also tried
whitout any result, i don'have forced any kind of version of this plugin, i don't know how to use it properly, a couple of week ago everything was fine.
Thanks