Benoît COUETIL
Benoît COUETIL
I forgot to mention that this is a mono-repository, so one project on Gitlab side and multiple projects on SonarQube side. I tested by adding deliberate code smalls to 2...
Although, I may use some outdated scanner fields : ``` sonar.pullrequest.key=$CI_MERGE_REQUEST_IID sonar.pullrequest.branch=$CI_MERGE_REQUEST_SOURCE_BRANCH_NAME sonar.pullrequest.base=$CI_MERGE_REQUEST_TARGET_BRANCH_NAME sonar.pullrequest.gitlab.instanceUrl=$CI_API_V4_URL sonar.pullrequest.gitlab.projectId=$CI_PROJECT_PATH sonar.pullrequest.gitlab.projectUrl=$CI_MERGE_REQUEST_PROJECT_URL com.github.mc1arke.sonarqube.plugin.branch.pullrequest.gitlab.pipelineId=$CI_PIPELINE_ID sonar.scm.revision=$CI_COMMIT_SHA ```
Thank you for your time. An example MR to show would be too complicated as of now, so here are debug logs : [sonarqube_ce(13).log](https://github.com/mc1arke/sonarqube-community-branch-plugin/files/9157782/sonarqube_ce.13.log)
Unfortunately no solution as of now... I guess @mc1arke has not found time to dig into this for now...
Same problem, coming here searching for a reason/fix :+1:
Gitlab relies on current commit for branch pipeline, and on new commits for MR pipeline. But gitlab-ci-local does not rely on commits, for us to run the tool without having...
Why don't you reference master instead of tags ?
Hello 😊 I may try to reproduce to help the cause, if I find time. Does it work with the `--force` flag ?